diff --git a/parts/chapters/subsections/5.3/AQUDIMS.fodt b/parts/chapters/subsections/5.3/AQUDIMS.fodt index eb65a7ea..2b4cae5c 100644 --- a/parts/chapters/subsections/5.3/AQUDIMS.fodt +++ b/parts/chapters/subsections/5.3/AQUDIMS.fodt @@ -4272,7 +4272,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.MXNAQC - 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. + 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. 1 @@ -4315,7 +4315,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.NANAQ - A positive integer value that defines the AQUFETP, AQUFLUX and AQUCT maximum number of analytical aquifers defined by these three keywords. + A positive integer value that defines the AQUFETP, AQUFLUX and AQUCT maximum number of analytical aquifers defined by these three keywords. 1 diff --git a/parts/chapters/subsections/5.3/CO2SOL.fodt b/parts/chapters/subsections/5.3/CO2SOL.fodt index cea9c7ef..5b9503ea 100644 --- a/parts/chapters/subsections/5.3/CO2SOL.fodt +++ b/parts/chapters/subsections/5.3/CO2SOL.fodt @@ -4205,7 +4205,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.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. The CO2SOL keyword can be used when modelling CO2 injection in depleted hydrocarbon reservoirs. See also the CO2STORE keyword in the RUNSPEC section which can be used when modelling CO2 injection in saline aquifers. The CO2-Brine PVT model computes the PVT properties such as density, viscosity, and enthalpy internally as functions of pressure, temperature, and composition by using analytic correlations and models from the literature rather than by interpolation of tabulated values in the input deck. These values are transformed to the standard black-oil equivalent PVT tables internally by the simulator. A full description of the underlying PVT models is described by Sandve et al.1 - 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.. Note that the CO2-Brine PVT properties depend on the temperature and salinity and these must therefore be entered in the PROPS section. The reservoir temperature can be defined using, e.g., the RTEMP keyword. Region based salinity can be provided using the SALINITY keyword. + 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.. Note that the CO2-Brine PVT properties depend on the temperature and salinity and these must therefore be entered in the PROPS section. The reservoir temperature can be defined using, e.g., the RTEMP keyword. Region based salinity can be provided using the SALINITY keyword. The CO2SOL keyword must be used together with the SOLVENT keyword in the RUNSPEC section. The SOLVENT keyword activates the four component black-oil model: oil, water and gas, plus a solvent (in this case CO2). The DISGASW keyword in the RUNSPEC section can be used to model dissolution of CO2 in the Brine. Note that hydrocarbon gas is not allowed to dissolve in the Brine (this is considered a reasonable assumption for most hydrocarbon gases). The hydrocarbon reservoir fluid properties should be set up as normal apart from the water PVT properties, which will be defined by the simulators’ CO2-Brine PVT model, so the water PVT keywords (e.g. PVTW) are not required. The CO2 PVT properties will also be defined by the CO2-Brine PVT model so the solvent PVT keywords (e.g. SDENSITY, PVTSOL) are also not required. @@ -4238,7 +4238,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- DISGASW - The 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. + The 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. -- ============================================================================== -- -- PROPS SECTION diff --git a/parts/chapters/subsections/5.3/CO2STORE.fodt b/parts/chapters/subsections/5.3/CO2STORE.fodt index 30456e93..3bebc4e5 100644 --- a/parts/chapters/subsections/5.3/CO2STORE.fodt +++ b/parts/chapters/subsections/5.3/CO2STORE.fodt @@ -4425,7 +4425,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Description 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. The CO2-Brine PVT model computes the PVT properties such as density, viscosity, and enthalpy internally as functions of pressure, temperature, and composition by using analytic correlations and models from the literature rather than by interpolation from tabulated values. These values are transformed to the standard black-oil equivalent PVT tables internally by the simulator. A full description of the underlying PVT models is described by Sandve et al.1 - 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.. This means that the normal PVT keywords like DENSITY, PVTO, PVDG etc. are not required by OPM Flow when this model is activated, and if entered will be ignored by the simulator. Note that the CO2-Brine PVT properties depend on the temperature and salinity and these must therefore be entered in the PROPS section. The reservoir temperature can be defined using, e.g., the RTEMP keyword. Region based salinity can be provided using the SALINITY keyword. + 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.. This means that the normal PVT keywords like DENSITY, PVTO, PVDG etc. are not required by OPM Flow when this model is activated, and if entered will be ignored by the simulator. Note that the CO2-Brine PVT properties depend on the temperature and salinity and these must therefore be entered in the PROPS section. The reservoir temperature can be defined using, e.g., the RTEMP keyword. Region based salinity can be provided using the SALINITY keyword. The CO2STORE keyword must be used together with either: (1) the GAS and WATER keywords (or alternatively the GASWAT keyword), or (2) the GAS and OIL keywords in the RUNSPEC section. It is recommended that the standard method option (1) is used. The DISGASW keyword in the RUNSPEC section can be used with option (1) to model dissolution of CO2 in the Brine. Option (1) has the advantage that it can be used with the VAPWAT and PRECSALT keywords in the RUNSPEC section to model the impact of both vaporization of residual water and salt precipitation in the near wellbore region on injectivity of CO2 injection wells. diff --git a/parts/chapters/subsections/5.3/COLUMNS.fodt b/parts/chapters/subsections/5.3/COLUMNS.fodt index 64f41210..00195f42 100644 --- a/parts/chapters/subsections/5.3/COLUMNS.fodt +++ b/parts/chapters/subsections/5.3/COLUMNS.fodt @@ -4002,7 +4002,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. COLUMNS – Define Input File Column Margins - The COLUMNS keyword defines the input file column margins; characters outside the margins are ignored by the input parser. + The COLUMNS keyword defines the input file column margins; characters outside the margins are ignored by the input parser. See COLUMNS – Define Input File Column Marginsin the GLOBAL section for a full description. diff --git a/parts/chapters/subsections/5.3/ECHO.fodt b/parts/chapters/subsections/5.3/ECHO.fodt index 3cefaae6..77ca16af 100644 --- a/parts/chapters/subsections/5.3/ECHO.fodt +++ b/parts/chapters/subsections/5.3/ECHO.fodt @@ -4002,7 +4002,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. ECHO – Activate Echoing of User Input Files to the Print File - 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. + 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. See ECHO – Activate Echoing of User Input Files to the Print Filein the GLOBAL section for a full description. diff --git a/parts/chapters/subsections/5.3/END.fodt b/parts/chapters/subsections/5.3/END.fodt index 7fee9d38..301c71cd 100644 --- a/parts/chapters/subsections/5.3/END.fodt +++ b/parts/chapters/subsections/5.3/END.fodt @@ -3999,7 +3999,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. END – Define the End of the Input File - 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. + 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. See END – Define the End of the Input Filein the GLOBAL section for a full description. diff --git a/parts/chapters/subsections/5.3/ENDINC.fodt b/parts/chapters/subsections/5.3/ENDINC.fodt index edae5684..ea8f5793 100644 --- a/parts/chapters/subsections/5.3/ENDINC.fodt +++ b/parts/chapters/subsections/5.3/ENDINC.fodt @@ -4004,7 +4004,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. ENDINC – Define the End of an Include File - 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. + 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. See ENDINC – Define the End of an Include Filein the GLOBAL section for a full description. diff --git a/parts/chapters/subsections/5.3/ENDSKIP.fodt b/parts/chapters/subsections/5.3/ENDSKIP.fodt index dbf847d2..feb50cce 100644 --- a/parts/chapters/subsections/5.3/ENDSKIP.fodt +++ b/parts/chapters/subsections/5.3/ENDSKIP.fodt @@ -4013,7 +4013,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. ENDSKIP – DeActivate Skipping of Keywords and Input Data - 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. + 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. See ENDSKIP – DeActivate Skipping of Keywords and Input Datain the GLOBAL section for a full description. diff --git a/parts/chapters/subsections/5.3/EOS.fodt b/parts/chapters/subsections/5.3/EOS.fodt index 4bfb58cd..cda5acbc 100644 --- a/parts/chapters/subsections/5.3/EOS.fodt +++ b/parts/chapters/subsections/5.3/EOS.fodt @@ -4182,7 +4182,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. See EOS – Specify Equation of State in the PROPS section for a full description. diff --git a/parts/chapters/subsections/5.3/EQLDIMS.fodt b/parts/chapters/subsections/5.3/EQLDIMS.fodt index a29b3146..a85c3853 100644 --- a/parts/chapters/subsections/5.3/EQLDIMS.fodt +++ b/parts/chapters/subsections/5.3/EQLDIMS.fodt @@ -4365,7 +4365,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 5.11: EQLDIMS Keyword Description - It is common that the EQLNUM and FIPNUM arrays are identical so that the fluid in-place reporting matches the equilibration regions. Thus, in order to avoid errors in this case, one should just use one array (say the FIPNUM property array) and use the COPY keyword to generate the EQLNUM array. + It is common that the EQLNUM and FIPNUM arrays are identical so that the fluid in-place reporting matches the equilibration regions. Thus, in order to avoid errors in this case, one should just use one array (say the FIPNUM property array) and use the COPY keyword to generate the EQLNUM array. Example -- -- MAX MAX RSVD TVDP TVDP diff --git a/parts/chapters/subsections/5.3/EXTRAPMS.fodt b/parts/chapters/subsections/5.3/EXTRAPMS.fodt index 7ec1d5b2..26b37f5e 100644 --- a/parts/chapters/subsections/5.3/EXTRAPMS.fodt +++ b/parts/chapters/subsections/5.3/EXTRAPMS.fodt @@ -4002,7 +4002,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. EXTRAPMS – Activate Extrapolation Warning Messages - 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. + 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. See EXTRAPMS – Activate Extrapolation Warning Messagesin the GLOBAL section for a full description. diff --git a/parts/chapters/subsections/5.3/FORMFEED.fodt b/parts/chapters/subsections/5.3/FORMFEED.fodt index 3bf6004b..11351fb0 100644 --- a/parts/chapters/subsections/5.3/FORMFEED.fodt +++ b/parts/chapters/subsections/5.3/FORMFEED.fodt @@ -4002,7 +4002,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. FORMFEED – Defined the Print File Form-Feed Character - 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. + 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. See FORMFEED – Defined the Print File Form-Feed Characterin the GLOBAL section for a dull description. diff --git a/parts/chapters/subsections/5.3/GRIDOPTS.fodt b/parts/chapters/subsections/5.3/GRIDOPTS.fodt index 8c8a7502..c96071d2 100644 --- a/parts/chapters/subsections/5.3/GRIDOPTS.fodt +++ b/parts/chapters/subsections/5.3/GRIDOPTS.fodt @@ -4250,9 +4250,9 @@ Updated with AFR/TSA Rev-D comments and new keywords. 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. + 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. NO @@ -4268,7 +4268,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. 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. + Inter-region MULTNUM transmissibility multipliers can be defined using the MULTREGT and regional pore volumes multipliers can be set using the MULTREGP keyword. 0 @@ -4306,7 +4306,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 5.18: GRIDOPTS Keyword Description - See also the MULTNUM, MULTREGP, MULTREGT, PINCHNUM, and PINCHREG keywords. + See also the MULTNUM, MULTREGP, MULTREGT, PINCHNUM, and PINCHREG keywords. Example –- diff --git a/parts/chapters/subsections/5.3/H2SOL.fodt b/parts/chapters/subsections/5.3/H2SOL.fodt index 4bac22ec..73ccb272 100644 --- a/parts/chapters/subsections/5.3/H2SOL.fodt +++ b/parts/chapters/subsections/5.3/H2SOL.fodt @@ -4208,7 +4208,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Dedong Li, Christof Beyer, Sebastian Bauer, A unified phase equilibrium model for hydrogen solubility and solution density, International Journal of Hydrogen Energy, Volume 43, Issue 1, 2018, Pages 512-529.. Hydrogen gas density was modeled using Leachman et al.2 J. W. Leachman, R. T Jacobsen, S. G. Penoncello, E. W. Lemmon; Fundamental Equations of State for Parahydrogen, Normal Hydrogen, and Orthohydrogen. J. Phys. Chem. Ref. Data 1 September 2009; 38 (3): 721–748.. Other properties are modeled the same way as in CO2STORE but modified for hydrogen-brine (a similar approach was recently reported by Raad et al.3 Seyed Mostafa Jafari Raad, Ehsan Ranjbar, Hassan Hassanzadeh, Yuri Leonenko, Hydrogen-brine mixture PVT data for reservoir simulation of hydrogen storage in deep saline aquifers, International Journal of Hydrogen Energy, Volume 48, Issue 2, 2023, Pages 696-708.). A full description of the underlying PVT models used by CO2STORE is described by Sandve et al.4 - Tor Harald Sandve, 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.. Note that the H2-Brine PVT properties depend on the temperature and salinity and these must therefore be entered in the PROPS section. The reservoir temperature can be defined using, e.g., the RTEMP keyword. Region based salinity can be provided using the SALINITY keyword. + Tor Harald Sandve, 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.. Note that the H2-Brine PVT properties depend on the temperature and salinity and these must therefore be entered in the PROPS section. The reservoir temperature can be defined using, e.g., the RTEMP keyword. Region based salinity can be provided using the SALINITY keyword. The H2SOL keyword must be used together with the SOLVENT keyword in the RUNSPEC section. The SOLVENT keyword activates the four component black-oil model: oil, water and gas, plus a solvent (in this case H2). The DISGASW keyword in the RUNSPEC section can be used to model dissolution of H2 in the Brine. Note that hydrocarbon gas is not allowed to dissolve in the Brine (this is considered a reasonable assumption for most hydrocarbon gases). The hydrocarbon reservoir fluid properties should be set up as normal apart from the water PVT properties, which will be defined by the simulators’ H2-Brine PVT model, so the water PVT keywords (e.g. PVTW) are not required. The H2 PVT properties will also be defined by the H2-Brine PVT model so the solvent PVT keywords (e.g. SDENSITY, PVTSOL) are also not required. @@ -4241,7 +4241,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- DISGASW - The 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. + The 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. -- ============================================================================== -- -- PROPS SECTION diff --git a/parts/chapters/subsections/5.3/H2STORE.fodt b/parts/chapters/subsections/5.3/H2STORE.fodt index cff65342..f0b6f26a 100644 --- a/parts/chapters/subsections/5.3/H2STORE.fodt +++ b/parts/chapters/subsections/5.3/H2STORE.fodt @@ -4444,7 +4444,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Dedong Li, Christof Beyer, Sebastian Bauer, A unified phase equilibrium model for hydrogen solubility and solution density, International Journal of Hydrogen Energy, Volume 43, Issue 1, 2018, Pages 512-529.. Hydrogen gas density was modeled using Leachman et al.2 J. W. Leachman, R. T Jacobsen, S. G. Penoncello, E. W. Lemmon; Fundamental Equations of State for Parahydrogen, Normal Hydrogen, and Orthohydrogen. J. Phys. Chem. Ref. Data 1 September 2009; 38 (3): 721–748.. Other properties are modeled the same way as in CO2STORE but modified for hydrogen-brine (a similar approach was recently reported by Raad et al.3 Seyed Mostafa Jafari Raad, Ehsan Ranjbar, Hassan Hassanzadeh, Yuri Leonenko, Hydrogen-brine mixture PVT data for reservoir simulation of hydrogen storage in deep saline aquifers, International Journal of Hydrogen Energy, Volume 48, Issue 2, 2023, Pages 696-708.). A full description of the underlying PVT models used by CO2STORE is described by Sandve et al.4 - Tor Harald Sandve, 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.. This means that the normal PVT keywords like DENSITY, PVTO, PVDG etc. are not required by OPM Flow when this model is activated, and if entered will be ignored by the simulator. Note that the H2-Brine PVT properties depend on the temperature and salinity and these must therefore be entered in the PROPS section. The reservoir temperature can be defined using, e.g., the RTEMP keyword. Region based salinity can be provided using the SALINITY keyword. + Tor Harald Sandve, 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.. This means that the normal PVT keywords like DENSITY, PVTO, PVDG etc. are not required by OPM Flow when this model is activated, and if entered will be ignored by the simulator. Note that the H2-Brine PVT properties depend on the temperature and salinity and these must therefore be entered in the PROPS section. The reservoir temperature can be defined using, e.g., the RTEMP keyword. Region based salinity can be provided using the SALINITY keyword. The H2STORE keyword must be used with either: (1) the GAS and WATER keywords (or alternatively the GASWAT keyword), or (2) the GAS and OIL keywords in the RUNSPEC section. It is recommended that the standard option (1) is used. The DISGASW keyword can also be used with option (1) to model dissolution of H2 in the Brine. Option (1) has the advantage that it can be used with the VAPWAT and PRECSALT keywords to model the impact of both vaporization of residual water and salt precipitation in the near wellbore region on injectivity of H2 injection wells. diff --git a/parts/chapters/subsections/5.3/INCLUDE.fodt b/parts/chapters/subsections/5.3/INCLUDE.fodt index 346be889..7862feb3 100644 --- a/parts/chapters/subsections/5.3/INCLUDE.fodt +++ b/parts/chapters/subsections/5.3/INCLUDE.fodt @@ -3999,7 +3999,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. INCLUDE – Load Another Data File at the Current Position - 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. + 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. See INCLUDE – Load Another Data File at the Current Positionin the GLOBAL section for a full description. diff --git a/parts/chapters/subsections/5.3/LGRCOPY.fodt b/parts/chapters/subsections/5.3/LGRCOPY.fodt index 9119f768..80726678 100644 --- a/parts/chapters/subsections/5.3/LGRCOPY.fodt +++ b/parts/chapters/subsections/5.3/LGRCOPY.fodt @@ -4089,7 +4089,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - The LGRCOPY keyword actives Local Grid Refinement (“LGR”) Inheritance option that allows the LGR to inherit the properties of the global or host cell containing a LGR grid block at the start of the GRID section, as oppose 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 and EDIT sections the keyword must be placed inside a LGR definition section, that is between a CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) and the ENDFIN keyword. In the latter case inheritance is applied on an individual LGR basis. + The LGRCOPY keyword actives Local Grid Refinement (“LGR”) Inheritance option that allows the LGR to inherit the properties of the global or host cell containing a LGR grid block at the start of the GRID section, as oppose 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 and EDIT sections the keyword must be placed inside a LGR definition section, that is between a CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) and the ENDFIN keyword. In the latter case inheritance is applied on an individual LGR basis. Currently, OPM Flow does not support the local grid refinement feature and therefore this keyword is ignored by the simulator. Example The following example activates the LGR Inheritance option for all LGRs in the model. diff --git a/parts/chapters/subsections/5.3/LOAD.fodt b/parts/chapters/subsections/5.3/LOAD.fodt index a042d7be..085bab68 100644 --- a/parts/chapters/subsections/5.3/LOAD.fodt +++ b/parts/chapters/subsections/5.3/LOAD.fodt @@ -4083,7 +4083,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. diff --git a/parts/chapters/subsections/5.3/MESSAGE.fodt b/parts/chapters/subsections/5.3/MESSAGE.fodt index 2e1bc452..797eb81b 100644 --- a/parts/chapters/subsections/5.3/MESSAGE.fodt +++ b/parts/chapters/subsections/5.3/MESSAGE.fodt @@ -4005,7 +4005,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. MESSAGE – Output User Message - 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. + 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. See MESSAGE – Output User Messagein the GLOBAL section for a full description. diff --git a/parts/chapters/subsections/5.3/MESSAGES.fodt b/parts/chapters/subsections/5.3/MESSAGES.fodt index 5423cfad..080426f8 100644 --- a/parts/chapters/subsections/5.3/MESSAGES.fodt +++ b/parts/chapters/subsections/5.3/MESSAGES.fodt @@ -3995,7 +3995,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. MESSAGES – Define Message Print Limits and Stop Limits - 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. + 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. See MESSAGES – Define Message Print Limits and Stop Limitsin the GLOBAL section for a full description. diff --git a/parts/chapters/subsections/5.3/MINNPCOL.fodt b/parts/chapters/subsections/5.3/MINNPCOL.fodt index 986401e9..05d43aaf 100644 --- a/parts/chapters/subsections/5.3/MINNPCOL.fodt +++ b/parts/chapters/subsections/5.3/MINNPCOL.fodt @@ -4250,13 +4250,13 @@ Updated with AFR/TSA Rev-D comments and new keywords. Note - This is an OPM Flow specific keyword that sets the minimum number of Newton iterations, as opposed to the commercial simulator’s NUPCOL keyword that defines the maximum number of Newton iterations within a time step, after which well targets are frozen. + This is an OPM Flow specific keyword that sets the minimum number of Newton iterations, as opposed to the commercial simulator’s NUPCOL keyword that defines the maximum number of Newton iterations within a time step, after which well targets are frozen. - 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, the NUPCOL keyword in the RUNSPEC section can be used to set the maximum number of Newton iterations within a time step, after which the group well rates are frozen until the time step has converged. Reducing the potential for well rate oscillations within the time step may result in the group targets and limits not being exactly 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. Here, the MINNPCOL keyword sets the minimum number of Newton iterations within a timestep where the well production and injection targets may be updated. + 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, the NUPCOL keyword in the RUNSPEC section can be used to set the maximum number of Newton iterations within a time step, after which the group well rates are frozen until the time step has converged. Reducing the potential for well rate oscillations within the time step may result in the group targets and limits not being exactly 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. Here, the MINNPCOL keyword sets the minimum number of Newton iterations within a timestep where the well production and injection targets may be updated. See also section 2.2Running OPM Flow 2023-04 From The Command Lineon how to set various other numerical control parameters for OPM Flow. @@ -4286,7 +4286,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. A positive integer that defines the minimum number of Newton iterations within a timestep where well targets may be updated. - Note that the default value of six is higher than the commercial black-oil simulator’s default maximum value of three used on the NUPCOL keyword in the RUNSPEC section. + Note that the default value of six is higher than the commercial black-oil simulator’s default maximum value of three used on the NUPCOL keyword in the RUNSPEC section. 6 @@ -4321,4 +4321,4 @@ Updated with AFR/TSA Rev-D comments and new keywords. - + \ No newline at end of file diff --git a/parts/chapters/subsections/5.3/MONITOR.fodt b/parts/chapters/subsections/5.3/MONITOR.fodt index 9ab22a00..bbfe93ce 100644 --- a/parts/chapters/subsections/5.3/MONITOR.fodt +++ b/parts/chapters/subsections/5.3/MONITOR.fodt @@ -4070,7 +4070,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. Hence, OPM Flow ignores this keyword but it is documented here for completeness. There is no data required for this keyword and there is no terminating “/” for this keyword. Example diff --git a/parts/chapters/subsections/5.3/NODPPM.fodt b/parts/chapters/subsections/5.3/NODPPM.fodt index 4946bd11..ef7c7ec3 100644 --- a/parts/chapters/subsections/5.3/NODPPM.fodt +++ b/parts/chapters/subsections/5.3/NODPPM.fodt @@ -4086,7 +4086,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. There is no data required for this keyword and there is no terminating “/” for this keyword. Example diff --git a/parts/chapters/subsections/5.3/NOECHO.fodt b/parts/chapters/subsections/5.3/NOECHO.fodt index bf8d5bde..82bd7200 100644 --- a/parts/chapters/subsections/5.3/NOECHO.fodt +++ b/parts/chapters/subsections/5.3/NOECHO.fodt @@ -4002,7 +4002,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. NOECHO – Deactivate Echoing of User Input Files to the Print File - 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. + 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. See NOECHO – Deactivate Echoing of User Input Files to the Print Filein the GLOBAL section for a full description. diff --git a/parts/chapters/subsections/5.3/NOMONITO.fodt b/parts/chapters/subsections/5.3/NOMONITO.fodt index da295a6f..9bb14116 100644 --- a/parts/chapters/subsections/5.3/NOMONITO.fodt +++ b/parts/chapters/subsections/5.3/NOMONITO.fodt @@ -4073,7 +4073,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. Hence, OPM Flow ignores this keyword but it is documented here for completeness. There is no data required for this keyword and there is no terminating “/” for this keyword. Example diff --git a/parts/chapters/subsections/5.3/NOSIM.fodt b/parts/chapters/subsections/5.3/NOSIM.fodt index fae07b02..3d5c2332 100644 --- a/parts/chapters/subsections/5.3/NOSIM.fodt +++ b/parts/chapters/subsections/5.3/NOSIM.fodt @@ -4136,7 +4136,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. There is no data required for this keyword and there is no terminating “/” for this keyword. Example The example below switches OPM Flow to no simulation mode for data checking of the input deck. @@ -4145,7 +4145,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- NOSIM - And the next example shows how to commented out the NOSIM activation keyword so that the simulation will proceed. + And the next example shows how to commented out the NOSIM activation keyword so that the simulation will proceed. -- -- SWITCH NO SIMULATION MODE FOR DATA CHECKING COMMENT OUT TO RUN THE MODEL -- @@ -4157,8 +4157,8 @@ Updated with AFR/TSA Rev-D comments and new keywords. 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. + 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. diff --git a/parts/chapters/subsections/5.3/NOWARN.fodt b/parts/chapters/subsections/5.3/NOWARN.fodt index 4571c067..54a87b86 100644 --- a/parts/chapters/subsections/5.3/NOWARN.fodt +++ b/parts/chapters/subsections/5.3/NOWARN.fodt @@ -4002,7 +4002,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. NOWARN – Deactivate Warning Messages - 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. + 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. See NOWARN – Deactivate Warning Messagesin the GLOBAL section for a full description. diff --git a/parts/chapters/subsections/5.3/NUPCOL.fodt b/parts/chapters/subsections/5.3/NUPCOL.fodt index c1e24ae2..e5476f52 100644 --- a/parts/chapters/subsections/5.3/NUPCOL.fodt +++ b/parts/chapters/subsections/5.3/NUPCOL.fodt @@ -4221,8 +4221,8 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. - 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 for well rate oscillations within the time step may result in the group targets and limits not being exactly met in this case. Increasing the value of NUPCOL to greater than the default value of 12, will improve the accuracy of the group targets and limits at the expense of computational efficiency. + 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. + 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 for well rate oscillations within the time step may result in the group targets and limits not being exactly met in this case. Increasing the value of NUPCOL to greater than the default value of 12, will improve the accuracy of the group targets and limits at the expense of computational efficiency. See also section 2.2Running OPM Flow 2023-04 From The Command Lineon how to set various other numerical control parameters for OPM Flow. @@ -4248,7 +4248,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 - NUPCOL + NUPCOL A positive integer that defines the maximum number of Newton iterations used to update well targets within a time step. @@ -4282,10 +4282,10 @@ Updated with AFR/TSA Rev-D comments and new keywords.NUPCOL 12 / - The above example sets the NUPCOL value to its default value of 12. + The above example sets the NUPCOL value to its default value of 12. - + \ No newline at end of file diff --git a/parts/chapters/subsections/5.3/PATHS.fodt b/parts/chapters/subsections/5.3/PATHS.fodt index b7aa9fa5..a4d824f2 100644 --- a/parts/chapters/subsections/5.3/PATHS.fodt +++ b/parts/chapters/subsections/5.3/PATHS.fodt @@ -4241,7 +4241,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4316,7 +4316,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.'SCHD' '/DISK1/NORNE/2017/SCHD-INCLUDES' / / - The 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. + The 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. -- -- LOAD INCLUDE FILES -- diff --git a/parts/chapters/subsections/5.3/REGDIMS.fodt b/parts/chapters/subsections/5.3/REGDIMS.fodt index dfdf3b0d..065f347c 100644 --- a/parts/chapters/subsections/5.3/REGDIMS.fodt +++ b/parts/chapters/subsections/5.3/REGDIMS.fodt @@ -4376,7 +4376,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.NWKDREG - 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. + 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. 0 @@ -4390,7 +4390,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.NWKIREG - 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. + 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. 0 diff --git a/parts/chapters/subsections/5.3/SAVE.fodt b/parts/chapters/subsections/5.3/SAVE.fodt index 8dc68199..a8e34a19 100644 --- a/parts/chapters/subsections/5.3/SAVE.fodt +++ b/parts/chapters/subsections/5.3/SAVE.fodt @@ -4120,7 +4120,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.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. OPM Flow does not support the SAVE file format for fast restarts like the commercial simulator, but instead writes a standard RESTART file at the requested time step in the SCHEDULE section, which can then be used to restart the simulation at a given point in time via the RESTART keyword in the RUNSPEC section. 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. + 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. -- ============================================================================== -- -- RUNSPEC SECTION diff --git a/parts/chapters/subsections/5.3/SKIP.fodt b/parts/chapters/subsections/5.3/SKIP.fodt index 14278105..132ead31 100644 --- a/parts/chapters/subsections/5.3/SKIP.fodt +++ b/parts/chapters/subsections/5.3/SKIP.fodt @@ -4002,7 +4002,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. SKIP – Activate Skipping of All Keywords and Input Data - 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. + 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. See SKIP – Activate Skipping of All Keywords and Input Datain the GLOBAL section for a full description. diff --git a/parts/chapters/subsections/5.3/SKIP100.fodt b/parts/chapters/subsections/5.3/SKIP100.fodt index ac5b8e00..35def6ff 100644 --- a/parts/chapters/subsections/5.3/SKIP100.fodt +++ b/parts/chapters/subsections/5.3/SKIP100.fodt @@ -4001,7 +4001,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. SKIP100 – Activate Skipping of Black-Oil Keywords and Input Data - 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. + 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. See SKIP100 – Activate Skipping of Keywords by Black-Oil Simulatorin the GLOBAL section for a full description. diff --git a/parts/chapters/subsections/5.3/SKIP300.fodt b/parts/chapters/subsections/5.3/SKIP300.fodt index e4644f19..c36a21e8 100644 --- a/parts/chapters/subsections/5.3/SKIP300.fodt +++ b/parts/chapters/subsections/5.3/SKIP300.fodt @@ -4000,7 +4000,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. SKIP300 – Activate Skipping of Keywords by Compositional Simulator - 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. + 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. See Error: Reference source not foundin the GLOBAL section for a full description. diff --git a/parts/chapters/subsections/5.3/TEMP.fodt b/parts/chapters/subsections/5.3/TEMP.fodt index a24bb228..5641daa5 100644 --- a/parts/chapters/subsections/5.3/TEMP.fodt +++ b/parts/chapters/subsections/5.3/TEMP.fodt @@ -4276,7 +4276,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description This keyword activates the temperature modeling option in the commercial simulator. There is no data required for this keyword. - The temperature option (TEMP keyword) and the thermal option (THERMAL keyword) are two separate modeling facilities in the commercial simulator, although some keywords can be used by both options, for example the RTEMP keyword. OPM Flow’s thermal implementation is based on solving the energy equation fully coupled with the black-oil equations so the results are not directly equivalent to the commercial simulator’s black-oil TEMP or compositional THERMAL formulations. To activate OPM Flow’s thermal implementation use the THERMAL keyword in the RUNSPEC section. + The temperature option (TEMP keyword) and the thermal option (THERMAL keyword) are two separate modeling facilities in the commercial simulator, although some keywords can be used by both options, for example the RTEMP keyword. OPM Flow’s thermal implementation is based on solving the energy equation fully coupled with the black-oil equations so the results are not directly equivalent to the commercial simulator’s black-oil TEMP or compositional THERMAL formulations. To activate OPM Flow’s thermal implementation use the THERMAL keyword in the RUNSPEC section. OPM Flow treats the TEMP keyword as an alias for the THERMAL keyword, although it is recommended that the THERMAL keyword is used instead. Example -- diff --git a/parts/chapters/subsections/5.3/THERMAL.fodt b/parts/chapters/subsections/5.3/THERMAL.fodt index 4717908a..6d2c95a0 100644 --- a/parts/chapters/subsections/5.3/THERMAL.fodt +++ b/parts/chapters/subsections/5.3/THERMAL.fodt @@ -5450,7 +5450,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description This keyword activates the thermal modeling option. There is no data required for this keyword. The energy black-oil implementation in OPM Flow is a mixture of the commercial simulators black-oil and the commercial simulators “compositional thermal” keywords, as well as some OPM Flow specific keywords. - The temperature option (TEMP keyword) and the thermal option (THERMAL keyword) are two separate modeling facilities in the commercial simulator, although some keywords can be used by both options, for example the RTEMP keyword. OPM Flow’s thermal implementation is based on solving the energy equation fully coupled with the black-oil equations so the results are not directly equivalent to the commercial simulator’s black-oil TEMP or compositional THERMAL formulations. + The temperature option (TEMP keyword) and the thermal option (THERMAL keyword) are two separate modeling facilities in the commercial simulator, although some keywords can be used by both options, for example the RTEMP keyword. OPM Flow’s thermal implementation is based on solving the energy equation fully coupled with the black-oil equations so the results are not directly equivalent to the commercial simulator’s black-oil TEMP or compositional THERMAL formulations. Keywords specifically associated with both OPM Flow’s THERMAL and the commercial simulators TEMP and THERMAL options are listed in Table 5.46for ease of reference. @@ -5885,7 +5885,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - RTEMP + RTEMP Constant Initial Reservoir Temperature. @@ -5903,7 +5903,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - RTEMPA + RTEMPA Constant Initial Reservoir Temperature. @@ -5921,7 +5921,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - RTEMPVD + RTEMPVD Initial Reservoir Temperature versus Depth. @@ -5993,7 +5993,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - TEMPVD + TEMPVD Initial Reservoir Temperature versus Depth. @@ -6123,7 +6123,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.SOLUTION - RTEMP + RTEMP Constant Initial Reservoir Temperature. @@ -6141,7 +6141,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - RTEMPA + RTEMPA Constant Initial Reservoir Temperature. @@ -6159,7 +6159,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - RTEMPVD + RTEMPVD Initial Reservoir Temperature versus Depth. @@ -6195,7 +6195,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - TEMPVD + TEMPVD Initial Reservoir Temperature versus Depth. diff --git a/parts/chapters/subsections/5.3/UNIFSAVE.fodt b/parts/chapters/subsections/5.3/UNIFSAVE.fodt index 4774dc33..20117956 100644 --- a/parts/chapters/subsections/5.3/UNIFSAVE.fodt +++ b/parts/chapters/subsections/5.3/UNIFSAVE.fodt @@ -4095,7 +4095,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. There is no data required for this keyword and there is no terminating “/” for this keyword. This keyword is not supported by OPM Flow but has no effect on the results so it will be ignored. @@ -4105,7 +4105,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- UNIFSAVE - The above example switches on writing of unified SAVE output files. + The above example switches on writing of unified SAVE output files. diff --git a/parts/chapters/subsections/5.3/WARN.fodt b/parts/chapters/subsections/5.3/WARN.fodt index 000f3c28..b72baa32 100644 --- a/parts/chapters/subsections/5.3/WARN.fodt +++ b/parts/chapters/subsections/5.3/WARN.fodt @@ -4008,7 +4008,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. WARN – Activate Warning Messages - 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. + 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. See WARN – Activate Warning Messagesin the GLOBAL section for a full description.