diff --git a/parts/chapters/subsections/6.3/ACTNUM.fodt b/parts/chapters/subsections/6.3/ACTNUM.fodt index 0e1c000b..87f76012 100644 --- a/parts/chapters/subsections/6.3/ACTNUM.fodt +++ b/parts/chapters/subsections/6.3/ACTNUM.fodt @@ -4193,7 +4193,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description ACTNUM specifies which grid blocks are active or inactive. A value of 1 indicates the block is active and a value of 0 indicates the block is inactive. A grid block is inactive if its pore volume is less than the value entered using keyword MINPV. This keyword can be used to make blocks with a pore volume greater than MINPV inactive. Note that a value must be entered for each grid block in the model. Grid blocks are ordered with the I index cycling fastest, followed by the J and K indices. As for all array data repeat counts may be used, for example 100*1; however the full array must be specified. - Note that a cells activity can also be set using the EQUALS keyword by selection of only those cells that are required to be made inactive. + Note that a cells activity can also be set using the EQUALS keyword by selection of only those cells that are required to be made inactive. @@ -4232,7 +4232,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX keyword.. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX keyword.. The keyword is terminated by a “/”. @@ -4261,7 +4261,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 1 1 1 0 0 0 0 / - Alternatively the EQUALS keyword could be employed to accomplish the same task, that is: + Alternatively the EQUALS keyword could be employed to accomplish the same task, that is: -- -- ARRAY CONSTANT -- ---------- BOX --------- -- I1 I2 J1 J2 K1 K2 diff --git a/parts/chapters/subsections/6.3/ADD.fodt b/parts/chapters/subsections/6.3/ADD.fodt index 7ee11025..1b00bf38 100644 --- a/parts/chapters/subsections/6.3/ADD.fodt +++ b/parts/chapters/subsections/6.3/ADD.fodt @@ -4565,7 +4565,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4725,7 +4725,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - ADD Keyword and Variable Options by Section + ADD Keyword and Variable Options by Section @@ -4898,7 +4898,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTX + MULTX DIFFY @@ -4921,7 +4921,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTY + MULTY DIFFZ @@ -4944,7 +4944,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTZ + MULTZ TRANR @@ -5311,7 +5311,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - Table 6.4: ADD Keyword Applicable Arrays by Section + Table 6.4: ADD Keyword Applicable Arrays by Section Example -- -- ARRAY CONSTANT ---------- BOX --------- diff --git a/parts/chapters/subsections/6.3/ADDREG.fodt b/parts/chapters/subsections/6.3/ADDREG.fodt index a290595d..e953d857 100644 --- a/parts/chapters/subsections/6.3/ADDREG.fodt +++ b/parts/chapters/subsections/6.3/ADDREG.fodt @@ -4580,7 +4580,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4700,7 +4700,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - ADDREG Keyword and Variable Options by Section + ADDREG Keyword and Variable Options by Section @@ -4873,7 +4873,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTX + MULTX DIFFY @@ -4897,7 +4897,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTY + MULTY DIFFZ @@ -4920,7 +4920,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTZ + MULTZ TRANR @@ -5287,7 +5287,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - Table 6.6: ADDREG Keyword Applicable Arrays by Section + Table 6.6: ADDREG Keyword Applicable Arrays by Section Example -- -- FIRST DEFINE THE PROPERTY ARRAYS AND MULTNUM ARRAYS FOR 10 X 10 X 20 MODEL @@ -5315,7 +5315,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.PERMX 100.0 2 M / PERMX -50.00 3 M / / - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/AQUANCON.fodt b/parts/chapters/subsections/6.3/AQUANCON.fodt index 935af57d..2b1cbd64 100644 --- a/parts/chapters/subsections/6.3/AQUANCON.fodt +++ b/parts/chapters/subsections/6.3/AQUANCON.fodt @@ -4296,8 +4296,8 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. - Note that numerical aquifers are connected to the grid using the AQUCON keyword in the GRID section and that both aquifer types dimensions are declared by the AQUDIMS keyword in the RUNSPEC section. + 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. + Note that numerical aquifers are connected to the grid using the AQUCON keyword in the GRID section and that both aquifer types dimensions are declared by the AQUDIMS keyword in the RUNSPEC section. @@ -4584,7 +4584,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. 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. + 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. @@ -4608,7 +4608,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 61 61 48 72 12 17 'I+' 1* 1* 'NO' / / - See the AQUCT keyword in the GRID section for a complete example on defining and connecting a Carter-Tracy aquifer to a simulation grid. + See the AQUCT keyword in the GRID section for a complete example on defining and connecting a Carter-Tracy aquifer to a simulation grid. diff --git a/parts/chapters/subsections/6.3/AQUCON.fodt b/parts/chapters/subsections/6.3/AQUCON.fodt index 7a78cef8..5daae14e 100644 --- a/parts/chapters/subsections/6.3/AQUCON.fodt +++ b/parts/chapters/subsections/6.3/AQUCON.fodt @@ -4352,7 +4352,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4683,7 +4683,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. 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. + 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. diff --git a/parts/chapters/subsections/6.3/AQUCT.fodt b/parts/chapters/subsections/6.3/AQUCT.fodt index 59471ac8..afe34ba1 100644 --- a/parts/chapters/subsections/6.3/AQUCT.fodt +++ b/parts/chapters/subsections/6.3/AQUCT.fodt @@ -4483,10 +4483,10 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - The AQUCT keyword defines Carter-Tracy112 + The AQUCT keyword defines Carter-Tracy112 Carter, R. D. and Tracy, G. W. “An Improved Method for Calculating Water Influx,” Transactions of AIME (1960) 219, 215-417. and 113 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. - Each row entry in the AQUCT keyword defines one Carter-Tracy aquifer. + Each row entry in the AQUCT keyword defines one Carter-Tracy aquifer. @@ -4914,7 +4914,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - In order to full define a Carter-Tracy aquifer one has to define the aquifer properties via the AQUCT keyword, the Carter-Tracy influence function via the AQUTAB keyword in the PROPS section (AQUTAB – Define Carter-Tracy Aquifer Influence Functions), if the default infinite acting table is not being employed, and finally, how the aquifer is connected to the reservoir using the AQUANCON keyword in the GRID or SOLUTION sections. + In order to full define a Carter-Tracy aquifer one has to define the aquifer properties via the AQUCT keyword, the Carter-Tracy influence function via the AQUTAB keyword in the PROPS section (AQUTAB – Define Carter-Tracy Aquifer Influence Functions), if the default infinite acting table is not being employed, and finally, how the aquifer is connected to the reservoir using the AQUANCON keyword in the GRID or SOLUTION sections. Example Given the following grid and aquifer dimensions in the RUNSPEC section: -- diff --git a/parts/chapters/subsections/6.3/AQUNUM.fodt b/parts/chapters/subsections/6.3/AQUNUM.fodt index 063ef523..390504ee 100644 --- a/parts/chapters/subsections/6.3/AQUNUM.fodt +++ b/parts/chapters/subsections/6.3/AQUNUM.fodt @@ -4637,7 +4637,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.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. + 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. @@ -4874,8 +4874,8 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.10: AQUNUM Keyword Description - Numerical aquifers ares modeled as one-dimensional, with aquifer flow assumed to be in the direction defined by LENGTH, and flux out of the aquifer is through the cross sectional area defined by AREA. Note that, all the aquifer cells must be isolated from the reservoir cells, with only the AQUCON connections connecting to the actual reservoir cells. - The values entered on the AQUNUM keyword are used to calculate the aquifer's pore volume and the transmissibility between the aquifer and the connected cell faces defined on the AQUCON keyword. Thus: + Numerical aquifers ares modeled as one-dimensional, with aquifer flow assumed to be in the direction defined by LENGTH, and flux out of the aquifer is through the cross sectional area defined by AREA. Note that, all the aquifer cells must be isolated from the reservoir cells, with only the AQUCON connections connecting to the actual reservoir cells. + The values entered on the AQUNUM keyword are used to calculate the aquifer's pore volume and the transmissibility between the aquifer and the connected cell faces defined on the AQUCON keyword. Thus: @@ -4937,21 +4937,21 @@ Updated with AFR/TSA Rev-D comments and new keywords.and any modifications to the host cell values performed in either the GRID or EDIT sections are always ignored for cells declared as numerical aquifers cells. - For the transmissibility calculation either the cross-sectional area (AREA) defined on the AQUNUM keyword may be used or the connecting cell cross-sectional area by setting the AQUOPT1 variable on the AQUCON keyword. + For the transmissibility calculation either the cross-sectional area (AREA) defined on the AQUNUM keyword may be used or the connecting cell cross-sectional area by setting the AQUOPT1 variable on the AQUCON keyword. - In order to full define a numerical aquifer one has to define the aquifer properties via the AQUNUM keyword, and how the aquifer is connected to the reservoir using the AQUCON keyword in the GRID or SOLUTION sections. + In order to full define a numerical aquifer one has to define the aquifer properties via the AQUNUM keyword, and how the aquifer is connected to the reservoir using the AQUCON keyword in the GRID or SOLUTION sections. 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. + 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. diff --git a/parts/chapters/subsections/6.3/BOUNDARY.fodt b/parts/chapters/subsections/6.3/BOUNDARY.fodt index e03e45fe..32807b08 100644 --- a/parts/chapters/subsections/6.3/BOUNDARY.fodt +++ b/parts/chapters/subsections/6.3/BOUNDARY.fodt @@ -4073,7 +4073,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. 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/6.3/BOX.fodt b/parts/chapters/subsections/6.3/BOX.fodt index 9d482192..df3dd381 100644 --- a/parts/chapters/subsections/6.3/BOX.fodt +++ b/parts/chapters/subsections/6.3/BOX.fodt @@ -4261,8 +4261,8 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. - Note that the BOX grid is reset by the keyword ENDBOX by resetting the current defined BOX to be the whole grid. The keyword can be used for any array and for all grid types. + 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. + Note that the BOX grid is reset by the keyword ENDBOX by resetting the current defined BOX to be the whole grid. The keyword can be used for any array and for all grid types. @@ -4385,7 +4385,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.11: BOX Keyword Description - See also the ADD, COPY, ENDBOX, EQUALS, and MULTIPLY keywords can also be used to enter data in a subset of the model. + See also the ADD, COPY, ENDBOX, EQUALS, and MULTIPLY keywords can also be used to enter data in a subset of the model. Examples -- @@ -4409,8 +4409,8 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. - Alternatively, one could use the EQUALS keyword to accomplish the same thing. + The 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. + Alternatively, one could use the EQUALS keyword to accomplish the same thing. -- -- ARRAY CONSTANT -- ---------- BOX --------- -- I1 I2 J1 J2 K1 K2 EQUALS @@ -4426,7 +4426,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. 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. + 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. diff --git a/parts/chapters/subsections/6.3/CARFIN.fodt b/parts/chapters/subsections/6.3/CARFIN.fodt index c1e0c295..80bf5730 100644 --- a/parts/chapters/subsections/6.3/CARFIN.fodt +++ b/parts/chapters/subsections/6.3/CARFIN.fodt @@ -4240,7 +4240,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. 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/6.3/COLUMNS.fodt b/parts/chapters/subsections/6.3/COLUMNS.fodt index bade49ea..5b2a99a6 100644 --- a/parts/chapters/subsections/6.3/COLUMNS.fodt +++ b/parts/chapters/subsections/6.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/6.3/COPY.fodt b/parts/chapters/subsections/6.3/COPY.fodt index bfd3aeb2..2d9f29bc 100644 --- a/parts/chapters/subsections/6.3/COPY.fodt +++ b/parts/chapters/subsections/6.3/COPY.fodt @@ -4556,7 +4556,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4716,7 +4716,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - COPY Keyword and Variable Options by Section + COPY Keyword and Variable Options by Section @@ -4889,7 +4889,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTX + MULTX DIFFY @@ -4912,7 +4912,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTY + MULTY DIFFZ @@ -4935,7 +4935,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTZ + MULTZ TRANR @@ -5302,7 +5302,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - Table 6.17: COPY Keyword Applicable Arrays by Section + Table 6.17: COPY Keyword Applicable Arrays by Section Example -- -- SOURCE DESTIN. ---------- BOX --------- diff --git a/parts/chapters/subsections/6.3/COPYBOX.fodt b/parts/chapters/subsections/6.3/COPYBOX.fodt index bc983431..7039db0b 100644 --- a/parts/chapters/subsections/6.3/COPYBOX.fodt +++ b/parts/chapters/subsections/6.3/COPYBOX.fodt @@ -5108,7 +5108,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTX + MULTX @@ -5131,7 +5131,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTY + MULTY @@ -5154,7 +5154,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTZ + MULTZ diff --git a/parts/chapters/subsections/6.3/COPYREG.fodt b/parts/chapters/subsections/6.3/COPYREG.fodt index fdc0d0e2..0fc15f2d 100644 --- a/parts/chapters/subsections/6.3/COPYREG.fodt +++ b/parts/chapters/subsections/6.3/COPYREG.fodt @@ -4624,7 +4624,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4744,7 +4744,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - COPYREG Keyword and Variable Options by Section + COPYREG Keyword and Variable Options by Section @@ -4918,7 +4918,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTX + MULTX DIFFY @@ -4941,7 +4941,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTY + MULTY DIFFZ @@ -4964,7 +4964,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTZ + MULTZ TRANR @@ -5331,7 +5331,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - Table 6.21: COPYREG Keyword Applicable Arrays by Section + Table 6.21: COPYREG Keyword Applicable Arrays by Section Example -- -- COPY AN ARRAY TO ANOTHER ARRAY BASED ON A REGION NUMBER @@ -5354,7 +5354,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.PERMX 0.95 1 M / / - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/DISPERC.fodt b/parts/chapters/subsections/6.3/DISPERC.fodt index 4bca3ab9..9621c516 100644 --- a/parts/chapters/subsections/6.3/DISPERC.fodt +++ b/parts/chapters/subsections/6.3/DISPERC.fodt @@ -4436,7 +4436,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/DR.fodt b/parts/chapters/subsections/6.3/DR.fodt index c28abd1a..01cf324c 100644 --- a/parts/chapters/subsections/6.3/DR.fodt +++ b/parts/chapters/subsections/6.3/DR.fodt @@ -4348,7 +4348,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The first layer (K=1) must always be fully defined; however, subsequent layers may be default and if defaulted they will take the values from the layer above. diff --git a/parts/chapters/subsections/6.3/DTHETA.fodt b/parts/chapters/subsections/6.3/DTHETA.fodt index 36bbf4b5..280c0a9c 100644 --- a/parts/chapters/subsections/6.3/DTHETA.fodt +++ b/parts/chapters/subsections/6.3/DTHETA.fodt @@ -4299,7 +4299,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/DX.fodt b/parts/chapters/subsections/6.3/DX.fodt index 1f622757..9de83581 100644 --- a/parts/chapters/subsections/6.3/DX.fodt +++ b/parts/chapters/subsections/6.3/DX.fodt @@ -4304,7 +4304,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/DY.fodt b/parts/chapters/subsections/6.3/DY.fodt index c7e7b664..59223f0b 100644 --- a/parts/chapters/subsections/6.3/DY.fodt +++ b/parts/chapters/subsections/6.3/DY.fodt @@ -4296,7 +4296,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/DZ.fodt b/parts/chapters/subsections/6.3/DZ.fodt index 42b216b7..2594c40d 100644 --- a/parts/chapters/subsections/6.3/DZ.fodt +++ b/parts/chapters/subsections/6.3/DZ.fodt @@ -4292,7 +4292,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/DZNET.fodt b/parts/chapters/subsections/6.3/DZNET.fodt index c49078c1..d197056b 100644 --- a/parts/chapters/subsections/6.3/DZNET.fodt +++ b/parts/chapters/subsections/6.3/DZNET.fodt @@ -4304,7 +4304,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/ECHO.fodt b/parts/chapters/subsections/6.3/ECHO.fodt index 59a09c44..62c5634f 100644 --- a/parts/chapters/subsections/6.3/ECHO.fodt +++ b/parts/chapters/subsections/6.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/6.3/END.fodt b/parts/chapters/subsections/6.3/END.fodt index 46ea095c..61f2a5fc 100644 --- a/parts/chapters/subsections/6.3/END.fodt +++ b/parts/chapters/subsections/6.3/END.fodt @@ -4007,7 +4007,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/6.3/ENDBOX.fodt b/parts/chapters/subsections/6.3/ENDBOX.fodt index 403fd624..2b1d0cd8 100644 --- a/parts/chapters/subsections/6.3/ENDBOX.fodt +++ b/parts/chapters/subsections/6.3/ENDBOX.fodt @@ -4112,7 +4112,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. There is no data required for this keyword. Example -- @@ -4133,7 +4133,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. @@ -4141,7 +4141,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. 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. + 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. diff --git a/parts/chapters/subsections/6.3/ENDFIN.fodt b/parts/chapters/subsections/6.3/ENDFIN.fodt index 30663945..2b85d168 100644 --- a/parts/chapters/subsections/6.3/ENDFIN.fodt +++ b/parts/chapters/subsections/6.3/ENDFIN.fodt @@ -4083,7 +4083,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. 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/6.3/ENDINC.fodt b/parts/chapters/subsections/6.3/ENDINC.fodt index b01e31a1..75251063 100644 --- a/parts/chapters/subsections/6.3/ENDINC.fodt +++ b/parts/chapters/subsections/6.3/ENDINC.fodt @@ -4002,7 +4002,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/6.3/ENDSKIP.fodt b/parts/chapters/subsections/6.3/ENDSKIP.fodt index c0e98c0e..5c1f8978 100644 --- a/parts/chapters/subsections/6.3/ENDSKIP.fodt +++ b/parts/chapters/subsections/6.3/ENDSKIP.fodt @@ -4018,7 +4018,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/6.3/EQUALREG.fodt b/parts/chapters/subsections/6.3/EQUALREG.fodt index b9bdfa5f..ba2a40da 100644 --- a/parts/chapters/subsections/6.3/EQUALREG.fodt +++ b/parts/chapters/subsections/6.3/EQUALREG.fodt @@ -4599,7 +4599,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. @@ -4720,7 +4720,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - EQUALREG Keyword and Variable Options by Section + EQUALREG Keyword and Variable Options by Section @@ -4894,7 +4894,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTX + MULTX DIFFY @@ -4917,7 +4917,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTY + MULTY DIFFZ @@ -4940,7 +4940,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTZ + MULTZ TRANR @@ -5307,7 +5307,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - Table 6.34: EQUALREG Keyword Applicable Arrays by Section + Table 6.34: EQUALREG Keyword Applicable Arrays by Section Example -- FIRST DEFINE MULTNUM ARRAYS FOR 10 X 10 X 20 MODEL -- @@ -5331,7 +5331,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.PERMX 75.00 2 M / PERMX 50.00 3 M / / - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/EQUALS.fodt b/parts/chapters/subsections/6.3/EQUALS.fodt index 9e7b3067..76a95eb2 100644 --- a/parts/chapters/subsections/6.3/EQUALS.fodt +++ b/parts/chapters/subsections/6.3/EQUALS.fodt @@ -4599,7 +4599,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4759,7 +4759,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - EQUALS Keyword and Variable Options by Section + EQUALS Keyword and Variable Options by Section @@ -4933,7 +4933,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTX + MULTX DIFFY @@ -4956,7 +4956,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTY + MULTY DIFFZ @@ -4979,7 +4979,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTZ + MULTZ TRANR @@ -5346,7 +5346,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - Table 6.36: EQUALS Keyword Applicable Arrays by Section + Table 6.36: EQUALS Keyword Applicable Arrays by Section @@ -5354,7 +5354,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Note - Unlike the commercial simulator, using the EQUALS keyword to setup the structure of the grid using the DX, DY, DZ and TOPS keywords should be avoided as it may cause OPM Flow to prematurely fail during the initialization. + Unlike the commercial simulator, using the EQUALS keyword to setup the structure of the grid using the DX, DY, DZ and TOPS keywords should be avoided as it may cause OPM Flow to prematurely fail during the initialization. See the second example on the correct way to setup this type of grid. @@ -5427,7 +5427,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.NTG 1.000 / / - Notice that the DX, DY, DZ and TOPS keywords are defined separately, that is they are not included in the EQUALS keyword. + Notice that the DX, DY, DZ and TOPS keywords are defined separately, that is they are not included in the EQUALS keyword. diff --git a/parts/chapters/subsections/6.3/EXTRAPMS.fodt b/parts/chapters/subsections/6.3/EXTRAPMS.fodt index 14cbf180..5cbb7d8c 100644 --- a/parts/chapters/subsections/6.3/EXTRAPMS.fodt +++ b/parts/chapters/subsections/6.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/6.3/FAULTS.fodt b/parts/chapters/subsections/6.3/FAULTS.fodt index 590ac2bf..478f0eba 100644 --- a/parts/chapters/subsections/6.3/FAULTS.fodt +++ b/parts/chapters/subsections/6.3/FAULTS.fodt @@ -4250,7 +4250,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4459,4 +4459,4 @@ Updated with AFR/TSA Rev-D comments and new keywords. - + \ No newline at end of file diff --git a/parts/chapters/subsections/6.3/FILEUNIT.fodt b/parts/chapters/subsections/6.3/FILEUNIT.fodt index f65a8954..2803b7a5 100644 --- a/parts/chapters/subsections/6.3/FILEUNIT.fodt +++ b/parts/chapters/subsections/6.3/FILEUNIT.fodt @@ -4210,7 +4210,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4235,7 +4235,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 - FILEUNIT + FILEUNIT A character string that defines the units of the data set, and should be set to: @@ -4274,7 +4274,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.38: FILEUNIT Keyword Description - OPM Flow's behavior is controllable through the "UNIT_SYSTEM_MISMATCH" environment variable. The default behavior if the check fails (i.e., if one of the INCLUDE files has a unit system different from the main run specification) is to terminate the simulation with an error. + OPM Flow's behavior is controllable through the "UNIT_SYSTEM_MISMATCH" environment variable. The default behavior if the check fails (i.e., if one of the INCLUDE files has a unit system different from the main run specification) is to terminate the simulation with an error. Example -- -- ACTIVATE UNIT CONSISTENCY CHECKING diff --git a/parts/chapters/subsections/6.3/FLUXNUM.fodt b/parts/chapters/subsections/6.3/FLUXNUM.fodt index 9d802f51..5c47c590 100644 --- a/parts/chapters/subsections/6.3/FLUXNUM.fodt +++ b/parts/chapters/subsections/6.3/FLUXNUM.fodt @@ -4242,7 +4242,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4282,7 +4282,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4305,7 +4305,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 / - Alternatively the EQUALS keyword could be employed to accomplish the same task, that is: + Alternatively the EQUALS keyword could be employed to accomplish the same task, that is: -- -- ARRAY CONSTANT ---------- BOX --------- -- I1 I2 J1 J2 K1 K2 diff --git a/parts/chapters/subsections/6.3/FORMFEED.fodt b/parts/chapters/subsections/6.3/FORMFEED.fodt index 4615cfb9..523585eb 100644 --- a/parts/chapters/subsections/6.3/FORMFEED.fodt +++ b/parts/chapters/subsections/6.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/6.3/GETDATA.fodt b/parts/chapters/subsections/6.3/GETDATA.fodt index 5681df2c..427b869c 100644 --- a/parts/chapters/subsections/6.3/GETDATA.fodt +++ b/parts/chapters/subsections/6.3/GETDATA.fodt @@ -4094,7 +4094,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. 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/6.3/HEATCR.fodt b/parts/chapters/subsections/6.3/HEATCR.fodt index 31c34fce..f5ecb9da 100644 --- a/parts/chapters/subsections/6.3/HEATCR.fodt +++ b/parts/chapters/subsections/6.3/HEATCR.fodt @@ -4288,7 +4288,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/HEATCRT.fodt b/parts/chapters/subsections/6.3/HEATCRT.fodt index 9d647e01..f6aa8968 100644 --- a/parts/chapters/subsections/6.3/HEATCRT.fodt +++ b/parts/chapters/subsections/6.3/HEATCRT.fodt @@ -4310,7 +4310,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/HMAQUNUM.fodt b/parts/chapters/subsections/6.3/HMAQUNUM.fodt index 45536140..23d68e81 100644 --- a/parts/chapters/subsections/6.3/HMAQUNUM.fodt +++ b/parts/chapters/subsections/6.3/HMAQUNUM.fodt @@ -4085,7 +4085,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. See also the HMDIMS keyword in the RUNSPEC section that specifies the dimensions for the gradient option, including the maximum number of aquifers that can be used with the History Match Gradient option. 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/6.3/HMMLAQUN.fodt b/parts/chapters/subsections/6.3/HMMLAQUN.fodt index 22ba3cfb..f21b0676 100644 --- a/parts/chapters/subsections/6.3/HMMLAQUN.fodt +++ b/parts/chapters/subsections/6.3/HMMLAQUN.fodt @@ -4090,7 +4090,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. Multipliers can be declared for numerical aquifers’ pore volume, permeability, and aquifer to grid connection factors. 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/6.3/HMMMREGT.fodt b/parts/chapters/subsections/6.3/HMMMREGT.fodt index 6b510325..bd60747d 100644 --- a/parts/chapters/subsections/6.3/HMMMREGT.fodt +++ b/parts/chapters/subsections/6.3/HMMMREGT.fodt @@ -4074,8 +4074,8 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. - Note that the HMMMREGT keyword only declares the two regions and the multiplier between those regions, the transmissibility direction (DIR on the MULTREGT keyword), type of transmissibility multiplier (TYPE on the MULTREGT keyword), and the region number array to use (ARRAY on the MULTREGT keyword), are all taken from the MULTREGY keyword. For example, 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, and before the HMMMREGT keyword is used. + 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. + Note that the HMMMREGT keyword only declares the two regions and the multiplier between those regions, the transmissibility direction (DIR on the MULTREGT keyword), type of transmissibility multiplier (TYPE on the MULTREGT keyword), and the region number array to use (ARRAY on the MULTREGT keyword), are all taken from the MULTREGY keyword. For example, 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, and before the HMMMREGT keyword is used. This keyword is not supported by OPM Flow but has no effect on the results so it will be ignored. diff --git a/parts/chapters/subsections/6.3/HMMULTFT.fodt b/parts/chapters/subsections/6.3/HMMULTFT.fodt index 703326f9..54e20f3b 100644 --- a/parts/chapters/subsections/6.3/HMMULTFT.fodt +++ b/parts/chapters/subsections/6.3/HMMULTFT.fodt @@ -4074,7 +4074,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. 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/6.3/HRFIN.fodt b/parts/chapters/subsections/6.3/HRFIN.fodt index 2a523a10..3c63bd54 100644 --- a/parts/chapters/subsections/6.3/HRFIN.fodt +++ b/parts/chapters/subsections/6.3/HRFIN.fodt @@ -4231,7 +4231,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description HRFIN116 - 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). + 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). 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/6.3/HXFIN.fodt b/parts/chapters/subsections/6.3/HXFIN.fodt index c437c001..fe389a34 100644 --- a/parts/chapters/subsections/6.3/HXFIN.fodt +++ b/parts/chapters/subsections/6.3/HXFIN.fodt @@ -4223,7 +4223,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. @@ -4313,7 +4313,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.47: HXFIN Keyword Description - See also the CARFIN, ENDFIN, HYFIN, and HZFIN keywords in the GRID section to fully define a Cartesian LGR grid model. + See also the CARFIN, ENDFIN, HYFIN, and HZFIN keywords in the GRID section to fully define a Cartesian LGR grid model. Example -- -- CARFIN LGR GRID COMMANDS diff --git a/parts/chapters/subsections/6.3/HYFIN.fodt b/parts/chapters/subsections/6.3/HYFIN.fodt index 859c0177..ffe87db2 100644 --- a/parts/chapters/subsections/6.3/HYFIN.fodt +++ b/parts/chapters/subsections/6.3/HYFIN.fodt @@ -4217,7 +4217,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. @@ -4307,7 +4307,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.48: HYFIN Keyword Description - See also the CARFIN, ENDFIN, HXFIN, and HZFIN keywords in the GRID section to fully define a Cartesian LGR grid model. + See also the CARFIN, ENDFIN, HXFIN, and HZFIN keywords in the GRID section to fully define a Cartesian LGR grid model. Example -- -- CARFIN LGR GRID COMMANDS diff --git a/parts/chapters/subsections/6.3/HZFIN.fodt b/parts/chapters/subsections/6.3/HZFIN.fodt index 93d0add3..d04db1c5 100644 --- a/parts/chapters/subsections/6.3/HZFIN.fodt +++ b/parts/chapters/subsections/6.3/HZFIN.fodt @@ -4220,7 +4220,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. @@ -4310,7 +4310,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.49: HZFIN Keyword Description - See also the CARFIN, ENDFIN, HXFIN, and HYFIN keywords in the GRID section to fully define a Cartesian LGR grid model. + See also the CARFIN, ENDFIN, HXFIN, and HYFIN keywords in the GRID section to fully define a Cartesian LGR grid model. Example -- -- CARFIN LGR GRID COMMANDS diff --git a/parts/chapters/subsections/6.3/IMPORT.fodt b/parts/chapters/subsections/6.3/IMPORT.fodt index 67150a8a..36a5ff3b 100644 --- a/parts/chapters/subsections/6.3/IMPORT.fodt +++ b/parts/chapters/subsections/6.3/IMPORT.fodt @@ -4219,7 +4219,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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 + 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 diff --git a/parts/chapters/subsections/6.3/INCLUDE.fodt b/parts/chapters/subsections/6.3/INCLUDE.fodt index feb9963a..25ccd3b7 100644 --- a/parts/chapters/subsections/6.3/INCLUDE.fodt +++ b/parts/chapters/subsections/6.3/INCLUDE.fodt @@ -4005,7 +4005,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/6.3/ISOLNUM.fodt b/parts/chapters/subsections/6.3/ISOLNUM.fodt index 92e6ee43..bc4e84f8 100644 --- a/parts/chapters/subsections/6.3/ISOLNUM.fodt +++ b/parts/chapters/subsections/6.3/ISOLNUM.fodt @@ -4259,7 +4259,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. Setting ISOLNUM for a cell to zero makes the cell inactive. diff --git a/parts/chapters/subsections/6.3/LGRCOPY.fodt b/parts/chapters/subsections/6.3/LGRCOPY.fodt index f8aaaf51..69e1ba89 100644 --- a/parts/chapters/subsections/6.3/LGRCOPY.fodt +++ b/parts/chapters/subsections/6.3/LGRCOPY.fodt @@ -3995,7 +3995,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. LGRCOPY – Activate Local Grid Refinement Inheritance - 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. See LGRCOPY – Activate Local Grid Refinement Inheritancein the RUNSPEC section for a full description. diff --git a/parts/chapters/subsections/6.3/LX.fodt b/parts/chapters/subsections/6.3/LX.fodt index 666f1e53..9881f046 100644 --- a/parts/chapters/subsections/6.3/LX.fodt +++ b/parts/chapters/subsections/6.3/LX.fodt @@ -4329,7 +4329,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x (NZ/2) parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x (NZ/2) parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4364,7 +4364,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS -- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/LXFIN.fodt b/parts/chapters/subsections/6.3/LXFIN.fodt index 45d07efa..45e4c5e5 100644 --- a/parts/chapters/subsections/6.3/LXFIN.fodt +++ b/parts/chapters/subsections/6.3/LXFIN.fodt @@ -4086,7 +4086,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. 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/6.3/LY.fodt b/parts/chapters/subsections/6.3/LY.fodt index 38085b1f..3d6f9f0b 100644 --- a/parts/chapters/subsections/6.3/LY.fodt +++ b/parts/chapters/subsections/6.3/LY.fodt @@ -4340,7 +4340,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x (NZ/2) parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x (NZ/2) parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4378,7 +4378,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/LYFIN.fodt b/parts/chapters/subsections/6.3/LYFIN.fodt index 0ce45b75..c66e8613 100644 --- a/parts/chapters/subsections/6.3/LYFIN.fodt +++ b/parts/chapters/subsections/6.3/LYFIN.fodt @@ -4086,7 +4086,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. 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/6.3/LZ.fodt b/parts/chapters/subsections/6.3/LZ.fodt index fcc3c8c3..584b556a 100644 --- a/parts/chapters/subsections/6.3/LZ.fodt +++ b/parts/chapters/subsections/6.3/LZ.fodt @@ -4327,7 +4327,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x (NZ/2) parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x (NZ/2) parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4365,7 +4365,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/LZFIN.fodt b/parts/chapters/subsections/6.3/LZFIN.fodt index 34131abb..df278df2 100644 --- a/parts/chapters/subsections/6.3/LZFIN.fodt +++ b/parts/chapters/subsections/6.3/LZFIN.fodt @@ -4086,7 +4086,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. 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/6.3/MAXVALUE.fodt b/parts/chapters/subsections/6.3/MAXVALUE.fodt index f87ef605..491579fb 100644 --- a/parts/chapters/subsections/6.3/MAXVALUE.fodt +++ b/parts/chapters/subsections/6.3/MAXVALUE.fodt @@ -4616,7 +4616,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4658,7 +4658,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.CONSTANT - 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 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. @@ -4778,7 +4778,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MAXVALUE Keyword and Variable Options by Section + MAXVALUE Keyword and Variable Options by Section @@ -4951,7 +4951,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTX + MULTX DIFFY @@ -4974,7 +4974,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTY + MULTY DIFFZ @@ -4997,7 +4997,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTZ + MULTZ TRANR @@ -5364,7 +5364,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - Table 6.61: MAXVALUE Keyword Applicable Arrays by Section + Table 6.61: MAXVALUE Keyword Applicable Arrays by Section Example -- -- ARRAY CONSTANT ---------- BOX --------- diff --git a/parts/chapters/subsections/6.3/MESSAGE.fodt b/parts/chapters/subsections/6.3/MESSAGE.fodt index 24a4adc9..e051c958 100644 --- a/parts/chapters/subsections/6.3/MESSAGE.fodt +++ b/parts/chapters/subsections/6.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/6.3/MESSAGES.fodt b/parts/chapters/subsections/6.3/MESSAGES.fodt index 6b195722..aeecc5da 100644 --- a/parts/chapters/subsections/6.3/MESSAGES.fodt +++ b/parts/chapters/subsections/6.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/6.3/MINPVV.fodt b/parts/chapters/subsections/6.3/MINPVV.fodt index 0f5bbfb4..a03fbe4c 100644 --- a/parts/chapters/subsections/6.3/MINPVV.fodt +++ b/parts/chapters/subsections/6.3/MINPVV.fodt @@ -4322,7 +4322,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4343,7 +4343,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.See also the PINCH keyword for the treatment of inactive grid cells and pinch-outs. 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. + 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. -- -- DEFINE A BOX GRID FOR THE BOTTOM TWO LAYERS OF A 100 X 100 X 20 MODEL -- @@ -4362,7 +4362,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.ENDBOX - Although 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. + Although 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. Instead one can use: -- diff --git a/parts/chapters/subsections/6.3/MINVALUE.fodt b/parts/chapters/subsections/6.3/MINVALUE.fodt index d5066c0d..0d0ad8ac 100644 --- a/parts/chapters/subsections/6.3/MINVALUE.fodt +++ b/parts/chapters/subsections/6.3/MINVALUE.fodt @@ -4619,7 +4619,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4661,7 +4661,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.CONSTANT - 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 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. @@ -4781,7 +4781,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - EQUALS Keyword and Variable Options by Section + EQUALS Keyword and Variable Options by Section @@ -4954,7 +4954,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTX + MULTX DIFFY @@ -4977,7 +4977,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTY + MULTY DIFFZ @@ -5000,7 +5000,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTZ + MULTZ TRANR @@ -5367,7 +5367,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - Table 6.66: MINVALUE Keyword Applicable Arrays by Section + Table 6.66: MINVALUE Keyword Applicable Arrays by Section Example -- -- ARRAY CONSTANT ---------- BOX --------- diff --git a/parts/chapters/subsections/6.3/MULTFLT.fodt b/parts/chapters/subsections/6.3/MULTFLT.fodt index 78a1385f..bad7e82d 100644 --- a/parts/chapters/subsections/6.3/MULTFLT.fodt +++ b/parts/chapters/subsections/6.3/MULTFLT.fodt @@ -4255,7 +4255,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. diff --git a/parts/chapters/subsections/6.3/MULTIPLY.fodt b/parts/chapters/subsections/6.3/MULTIPLY.fodt index 34dfde16..1a7dfff1 100644 --- a/parts/chapters/subsections/6.3/MULTIPLY.fodt +++ b/parts/chapters/subsections/6.3/MULTIPLY.fodt @@ -4549,7 +4549,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4710,7 +4710,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTIPLY Keyword and Variable Options by Section + MULTIPLY Keyword and Variable Options by Section @@ -4883,7 +4883,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTX + MULTX DIFFY @@ -4906,7 +4906,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTY + MULTY DIFFZ @@ -4929,7 +4929,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTZ + MULTZ TRANR @@ -5296,7 +5296,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - Table 6.69: MULTIPLY Keyword Applicable Arrays by Section + Table 6.69: MULTIPLY Keyword Applicable Arrays by Section Example -- -- ARRAY CONSTANT ---------- BOX --------- diff --git a/parts/chapters/subsections/6.3/MULTIREG.fodt b/parts/chapters/subsections/6.3/MULTIREG.fodt index b0445b8c..73e50dba 100644 --- a/parts/chapters/subsections/6.3/MULTIREG.fodt +++ b/parts/chapters/subsections/6.3/MULTIREG.fodt @@ -4570,7 +4570,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4863,7 +4863,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTX + MULTX DIFFY @@ -4887,7 +4887,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTY + MULTY DIFFZ @@ -4910,7 +4910,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTZ + MULTZ TRANR @@ -5277,7 +5277,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - Table 6.71: MULTIREG Keyword Applicable Arrays by Section + Table 6.71: MULTIREG Keyword Applicable Arrays by Section Example -- -- FIRST DEFINE THE PROPERTY ARRAYS AND MULTNUM ARRAYS FOR 10 X 10 X 20 MODEL @@ -5307,7 +5307,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.PERMX 0.90 3 M / / - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/MULTNUM.fodt b/parts/chapters/subsections/6.3/MULTNUM.fodt index 4566ff63..14bfb535 100644 --- a/parts/chapters/subsections/6.3/MULTNUM.fodt +++ b/parts/chapters/subsections/6.3/MULTNUM.fodt @@ -4206,7 +4206,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4246,7 +4246,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4268,7 +4268,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 / - Alternatively the EQUALS keyword could be employed to accomplish the same task, that is: + Alternatively the EQUALS keyword could be employed to accomplish the same task, that is: -- -- ARRAY CONSTANT ---------- BOX --------- -- I1 I2 J1 J2 K1 K2 diff --git a/parts/chapters/subsections/6.3/MULTPV.fodt b/parts/chapters/subsections/6.3/MULTPV.fodt index 8239db82..26c3d967 100644 --- a/parts/chapters/subsections/6.3/MULTPV.fodt +++ b/parts/chapters/subsections/6.3/MULTPV.fodt @@ -4206,7 +4206,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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). + 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). The keyword can be used for all grid types, except for the Radial Grid geometry. @@ -4232,10 +4232,10 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 - MULTPV + MULTPV - MULTPV is an array of real positive numbers assigning the pore volume multipliers for each cell in the model. + 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. @@ -4247,7 +4247,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4261,7 +4261,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.73: MULTPV Keyword Description - See also the MULTREGP keyword for scaling the cell pore volumes by region numbers. + See also the MULTREGP keyword for scaling the cell pore volumes by region numbers. Example -- -- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS @@ -4280,7 +4280,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/MULTR-.fodt b/parts/chapters/subsections/6.3/MULTR-.fodt index 90c2ef49..67b45c0d 100644 --- a/parts/chapters/subsections/6.3/MULTR-.fodt +++ b/parts/chapters/subsections/6.3/MULTR-.fodt @@ -4231,7 +4231,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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). + 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). The keyword should only be used with radial and spider grids, as declared by the RADIAL or SPIDER keywords in the RUNSPEC section. @@ -4257,10 +4257,10 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 - MULTR- + MULTR- - MULTR- is an array of real positive numbers assigning the transmissibility multipliers in the -R direction to each cell face in the model. + 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. @@ -4272,7 +4272,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4287,7 +4287,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Table 6.75: MULTR- Keyword Description Note that OPM Flow does not require the GRIDOPTS(TRANMULT) parameter in the RUNSPEC section to be set to YES, in order to use this and other negative directional dependent multiplier keywords in the input deck. Whereas, the commercial simulator will terminate with an error if the keyword is present, and the GRIDOPTS(TRANMULT) parameter has not been set to YES. - See also the MULTR, MULTTHT, MULTTHT-, MULTZ and MULTZ- keywords for scaling transmissible between cells in the R direction. + See also the MULTR, MULTTHT, MULTTHT-, MULTZ and MULTZ- keywords for scaling transmissible between cells in the R direction. Example -- -- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS @@ -4306,7 +4306,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/MULTR.fodt b/parts/chapters/subsections/6.3/MULTR.fodt index 8405b7b5..6df9556f 100644 --- a/parts/chapters/subsections/6.3/MULTR.fodt +++ b/parts/chapters/subsections/6.3/MULTR.fodt @@ -4228,7 +4228,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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). + 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). The keyword should only be used with radial and spider grids, as declared by the RADIAL or SPIDER keywords in the RUNSPEC section. @@ -4254,10 +4254,10 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 - MULTR+ + MULTR+ - MULTR+ is an array of real positive numbers assigning the transmissibility multipliers in the +R direction to each cell face in the model. + 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. @@ -4269,7 +4269,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4283,7 +4283,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.74: MULTR Keyword Description - See also the MULTR-, MULTTHT, MULTTHT-, MULTZ and MULTZ- keywords for scaling transmissible between between grid cells in the R direction. + See also the MULTR-, MULTTHT, MULTTHT-, MULTZ and MULTZ- keywords for scaling transmissible between between grid cells in the R direction. Example -- -- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS @@ -4302,7 +4302,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/MULTREGD.fodt b/parts/chapters/subsections/6.3/MULTREGD.fodt index 935988ef..d1f8ba41 100644 --- a/parts/chapters/subsections/6.3/MULTREGD.fodt +++ b/parts/chapters/subsections/6.3/MULTREGD.fodt @@ -4263,7 +4263,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. 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/6.3/MULTREGH.fodt b/parts/chapters/subsections/6.3/MULTREGH.fodt index 6a26bd31..c3794ac7 100644 --- a/parts/chapters/subsections/6.3/MULTREGH.fodt +++ b/parts/chapters/subsections/6.3/MULTREGH.fodt @@ -4266,7 +4266,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. 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/6.3/MULTREGP.fodt b/parts/chapters/subsections/6.3/MULTREGP.fodt index 22c1cb4e..fe2826c6 100644 --- a/parts/chapters/subsections/6.3/MULTREGP.fodt +++ b/parts/chapters/subsections/6.3/MULTREGP.fodt @@ -4215,7 +4215,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. diff --git a/parts/chapters/subsections/6.3/MULTREGT.fodt b/parts/chapters/subsections/6.3/MULTREGT.fodt index 5bd0639a..edc5db68 100644 --- a/parts/chapters/subsections/6.3/MULTREGT.fodt +++ b/parts/chapters/subsections/6.3/MULTREGT.fodt @@ -4278,7 +4278,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4443,7 +4443,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. 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. + 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. diff --git a/parts/chapters/subsections/6.3/MULTTHT-.fodt b/parts/chapters/subsections/6.3/MULTTHT-.fodt index ff16d503..4226d722 100644 --- a/parts/chapters/subsections/6.3/MULTTHT-.fodt +++ b/parts/chapters/subsections/6.3/MULTTHT-.fodt @@ -4223,7 +4223,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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). + 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). The keyword should only be used with radial and spider grids, as declared by the RADIAL or SPIDER keywords in the RUNSPEC section. @@ -4249,10 +4249,10 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 - MULTTHT- + MULTTHT- - MULTTHT- is an array of real positive numbers assigning the transmissibility multipliers in the -Theta direction to each cell face in the model. + 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. @@ -4264,7 +4264,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4279,7 +4279,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Table 6.81: MULTTHT- Keyword Description Note that OPM Flow does not require the GRIDOPTS(TRANMULT) parameter in the RUNSPEC section to be set to YES, in order to use this and other negative directional dependent multiplier keywords in the input deck. Whereas, the commercial simulator will terminate with an error if the keyword is present, and the GRIDOPTS(TRANMULT) parameter has not been set to YES. - See also the MULTTHT, MULTR, MULTR-, MULTZ and MULTZ- keywords for scaling transmissible between l grid cells in the Theta direction. + See also the MULTTHT, MULTR, MULTR-, MULTZ and MULTZ- keywords for scaling transmissible between l grid cells in the Theta direction. Example -- @@ -4299,7 +4299,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/MULTTHT.fodt b/parts/chapters/subsections/6.3/MULTTHT.fodt index 684fb831..68b98474 100644 --- a/parts/chapters/subsections/6.3/MULTTHT.fodt +++ b/parts/chapters/subsections/6.3/MULTTHT.fodt @@ -4228,7 +4228,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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). + 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). The keyword should only be used with radial and spider grids, as declared by the RADIAL or SPIDER keywords in the RUNSPEC section. @@ -4254,10 +4254,10 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 - MULTTHT+ + MULTTHT+ - MULTTHT+ is an array of real positive numbers assigning the transmissibility multipliers in the +Theta direction to each cell face in the model. + 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. @@ -4269,7 +4269,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4283,7 +4283,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.80: MULTTHT Keyword Description - See also the MULTTHT-, MULTR, MULTR-, MULTZ and MULTZ- keywords for scaling transmissible between l grid cells in the Theta direction. + See also the MULTTHT-, MULTR, MULTR-, MULTZ and MULTZ- keywords for scaling transmissible between l grid cells in the Theta direction. Example -- -- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS @@ -4302,7 +4302,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/MULTX-.fodt b/parts/chapters/subsections/6.3/MULTX-.fodt index 2f1ca2e7..371af9ae 100644 --- a/parts/chapters/subsections/6.3/MULTX-.fodt +++ b/parts/chapters/subsections/6.3/MULTX-.fodt @@ -4210,7 +4210,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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). + 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). The keyword can be used for all grid types, except for the Radial Grid geometry. @@ -4236,10 +4236,10 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 - MULTX- + MULTX- - MULTX- is an array of real positive numbers assigning the transmissibility multipliers in the -X direction to each cell face in the model. + 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. @@ -4251,7 +4251,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4266,7 +4266,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Table 6.83: MULTX- Keyword Description Note that OPM Flow does not require the GRIDOPTS(TRANMULT) parameter in the RUNSPEC section to be set to YES, in order to use this and other negative directional dependent multiplier keywords in the input deck. Whereas, the commercial simulator will terminate with an error if the keyword is present, and the GRIDOPTS(TRANMULT) parameter has not been set to YES. - See also the MULTX, MULTY, MULTY-, MULTZ and MULTZ- keywords for scaling transmissible between grid cells. + See also the MULTX, MULTY, MULTY-, MULTZ and MULTZ- keywords for scaling transmissible between grid cells. Example -- -- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS @@ -4285,7 +4285,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/MULTX.fodt b/parts/chapters/subsections/6.3/MULTX.fodt index fc96b780..f5083862 100644 --- a/parts/chapters/subsections/6.3/MULTX.fodt +++ b/parts/chapters/subsections/6.3/MULTX.fodt @@ -4214,8 +4214,8 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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). - 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). + 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). + 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). The keyword can be used for all grid types, except for the Radial Grid geometry. @@ -4241,10 +4241,10 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 - MULTX+ + MULTX+ - MULTX+ is an array of real positive numbers assigning the transmissibility multipliers in the +X direction to each cell face in the model. + 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. @@ -4256,7 +4256,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4270,7 +4270,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.82: MULTX Keyword Description - See also the MULTX-, MULTY, MULTY-, MULTZ and MULTZ- keywords for scaling transmissible between grid cells. + See also the MULTX-, MULTY, MULTY-, MULTZ and MULTZ- keywords for scaling transmissible between grid cells. Example -- -- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS @@ -4289,7 +4289,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/MULTY-.fodt b/parts/chapters/subsections/6.3/MULTY-.fodt index 14fb6cdc..0fb6e0c6 100644 --- a/parts/chapters/subsections/6.3/MULTY-.fodt +++ b/parts/chapters/subsections/6.3/MULTY-.fodt @@ -4213,7 +4213,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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). + 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). The keyword can be used for all grid types, except for the Radial Grid geometry. @@ -4239,10 +4239,10 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 - MULTY- + MULTY- - MULTY- is an array of real positive numbers assigning the transmissibility multipliers in the -Y direction to each cell face in the model. + 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. @@ -4254,7 +4254,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4269,7 +4269,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Table 6.85: MULTY- Keyword Description Note that OPM Flow does not require the GRIDOPTS(TRANMULT) parameter in the RUNSPEC section to be set to YES, in order to use this and other negative directional dependent multiplier keywords in the input deck. Whereas, the commercial simulator will terminate with an error if the keyword is present, and the GRIDOPTS(TRANMULT) parameter has not been set to YES. - See also the MULTY, MULTX, MULTX-, MULTZ and MULTZ- keywords for scaling transmissible between grid cells. + See also the MULTY, MULTX, MULTX-, MULTZ and MULTZ- keywords for scaling transmissible between grid cells. Example -- -- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS @@ -4288,7 +4288,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/MULTY.fodt b/parts/chapters/subsections/6.3/MULTY.fodt index f8c320c1..5dd9e0ae 100644 --- a/parts/chapters/subsections/6.3/MULTY.fodt +++ b/parts/chapters/subsections/6.3/MULTY.fodt @@ -4214,8 +4214,8 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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). - 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). + 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). + 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). The keyword can be used for all grid types, except for the Radial Grid geometry. @@ -4241,10 +4241,10 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 - MULTY+ + MULTY+ - MULTY+ is an array of real positive numbers assigning the transmissibility multipliers in the +Y direction to each cell face in the model. + 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. @@ -4256,7 +4256,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4270,7 +4270,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.84: MULTY Keyword Description - See also the MULTY-, MULTX, MULTX-, MULTZ and MULTZ- keywords for scaling transmissible between grid cells. + See also the MULTY-, MULTX, MULTX-, MULTZ and MULTZ- keywords for scaling transmissible between grid cells. Example -- -- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS @@ -4289,7 +4289,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/MULTZ-.fodt b/parts/chapters/subsections/6.3/MULTZ-.fodt index 9680fd9f..dc19e2b9 100644 --- a/parts/chapters/subsections/6.3/MULTZ-.fodt +++ b/parts/chapters/subsections/6.3/MULTZ-.fodt @@ -4216,7 +4216,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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). + 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). The keyword can be used for all grid types, except for the Radial Grid geometry. @@ -4242,10 +4242,10 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 - MULTZ- + MULTZ- - MULTZ- is an array of real positive numbers assigning the transmissibility multipliers in the -X direction to each cell face in the model. + 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. @@ -4257,7 +4257,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4272,7 +4272,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Table 6.87: MULTZ- Keyword Description Note that OPM Flow does not require the GRIDOPTS(TRANMULT) parameter in the RUNSPEC section to be set to YES, in order to use this and other negative directional dependent multiplier keywords in the input deck. Whereas, the commercial simulator will terminate with an error if the keyword is present, and the GRIDOPTS(TRANMULT) parameter has not been set to YES. - See also the MULTZ, MULTX, MULTX-, MULTY and MULTY- keywords for scaling transmissible between grid cells. + See also the MULTZ, MULTX, MULTX-, MULTY and MULTY- keywords for scaling transmissible between grid cells. Example -- -- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS @@ -4291,7 +4291,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/MULTZ.fodt b/parts/chapters/subsections/6.3/MULTZ.fodt index b1d1253e..3dff4012 100644 --- a/parts/chapters/subsections/6.3/MULTZ.fodt +++ b/parts/chapters/subsections/6.3/MULTZ.fodt @@ -4210,8 +4210,8 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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). - 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). + 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). + 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). The keyword can be used for all grid types, except for the Radial Grid geometry. @@ -4237,10 +4237,10 @@ Updated with AFR/TSA Rev-D comments and new keywords.1 - MULTZ+ + MULTZ+ - MULTZ+ is an array of real positive numbers assigning the transmissibility multipliers in the +Z direction to each cell face in the model. + 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. @@ -4252,7 +4252,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4266,7 +4266,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.86: MULTZ Keyword Description - See also the MULTZ-, MULTX, MULTX-, MULTY and MULTY- keywords for scaling transmissible between grid cells. + See also the MULTZ-, MULTX, MULTX-, MULTY and MULTY- keywords for scaling transmissible between grid cells. Example -- -- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS @@ -4285,7 +4285,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/NINENUM.fodt b/parts/chapters/subsections/6.3/NINENUM.fodt index 05be7128..9f73777e 100644 --- a/parts/chapters/subsections/6.3/NINENUM.fodt +++ b/parts/chapters/subsections/6.3/NINENUM.fodt @@ -4268,7 +4268,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/NNC.fodt b/parts/chapters/subsections/6.3/NNC.fodt index eb3f568e..8316c62b 100644 --- a/parts/chapters/subsections/6.3/NNC.fodt +++ b/parts/chapters/subsections/6.3/NNC.fodt @@ -4806,7 +4806,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Table 6.89: NNC Keyword Description Note that although items (8) to (17) for this keyword are not available in OPM Flow, even if they were, it is strongly recommended that these items are defaulted if the data is being entered manually, as opposed to being generated by a pre-processing software. Care should be taken that cells in different PVTNUM regions (see the PVTNUM keyword in the REGIONS section) are not connected, 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. - If the transmissibility across a fault needs to be modified see the FAULTS and MULTFLT keywords in the GRID section for an alternative and less complicated method to modifying fault transmissibilities. Transmissibility between reservoir regions can be modified by using MULTREGT keyword, provided MULTNUM has been used to define the inter-region transmissibility region numbers for each grid block. Finally, the MULTX, MULTY and MULTZ series of keywords can be used to modify transmissibility between various cells. All the aforementioned keywords are described in the GRID section. + If the transmissibility across a fault needs to be modified see the FAULTS and MULTFLT keywords in the GRID section for an alternative and less complicated method to modifying fault transmissibilities. Transmissibility between reservoir regions can be modified by using MULTREGT keyword, provided MULTNUM has been used to define the inter-region transmissibility region numbers for each grid block. Finally, the MULTX, MULTY and MULTZ series of keywords can be used to modify transmissibility between various cells. All the aforementioned keywords are described in the GRID section. Example -- -- MANUALLY DEFINE NON-NEIGHBOR CONNECTIONS diff --git a/parts/chapters/subsections/6.3/NODPPM.fodt b/parts/chapters/subsections/6.3/NODPPM.fodt index ff810da6..04ac6bf3 100644 --- a/parts/chapters/subsections/6.3/NODPPM.fodt +++ b/parts/chapters/subsections/6.3/NODPPM.fodt @@ -3996,7 +3996,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. NODPPM – Deactivate Fracture Porosity-Permeability Calculation - 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. See NODPPM – Deactivate Fracture Porosity-Permeability Calculationin the RUNSPEC section for a full description. diff --git a/parts/chapters/subsections/6.3/NOECHO.fodt b/parts/chapters/subsections/6.3/NOECHO.fodt index 398cca6c..f1d087d7 100644 --- a/parts/chapters/subsections/6.3/NOECHO.fodt +++ b/parts/chapters/subsections/6.3/NOECHO.fodt @@ -4001,7 +4001,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/6.3/NOWARN.fodt b/parts/chapters/subsections/6.3/NOWARN.fodt index 455064f6..be5e948c 100644 --- a/parts/chapters/subsections/6.3/NOWARN.fodt +++ b/parts/chapters/subsections/6.3/NOWARN.fodt @@ -4005,7 +4005,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/6.3/NXFIN.fodt b/parts/chapters/subsections/6.3/NXFIN.fodt index 219d89fa..a0322374 100644 --- a/parts/chapters/subsections/6.3/NXFIN.fodt +++ b/parts/chapters/subsections/6.3/NXFIN.fodt @@ -4217,7 +4217,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. @@ -4307,7 +4307,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.91: NXFIN Keyword Description - See also the CARFIN, ENDFIN, NYFIN, and NZFIN keywords in the GRID section to fully define a Cartesian LGR grid model. + See also the CARFIN, ENDFIN, NYFIN, and NZFIN keywords in the GRID section to fully define a Cartesian LGR grid model. Example -- -- CARFIN LGR GRID COMMANDS diff --git a/parts/chapters/subsections/6.3/NYFIN.fodt b/parts/chapters/subsections/6.3/NYFIN.fodt index 4c5fff8d..bc659f08 100644 --- a/parts/chapters/subsections/6.3/NYFIN.fodt +++ b/parts/chapters/subsections/6.3/NYFIN.fodt @@ -4217,7 +4217,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. @@ -4307,7 +4307,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.92: NYFIN Keyword Description - See also the CARFIN, ENDFIN, NXFIN, and NZFIN keywords in the GRID section to fully define a Cartesian LGR grid model. + See also the CARFIN, ENDFIN, NXFIN, and NZFIN keywords in the GRID section to fully define a Cartesian LGR grid model. Example -- -- CARFIN LGR GRID COMMANDS diff --git a/parts/chapters/subsections/6.3/NZFIN.fodt b/parts/chapters/subsections/6.3/NZFIN.fodt index cdeff35e..d3306185 100644 --- a/parts/chapters/subsections/6.3/NZFIN.fodt +++ b/parts/chapters/subsections/6.3/NZFIN.fodt @@ -4217,7 +4217,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. @@ -4307,7 +4307,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.93: NZFIN Keyword Description - See also the CARFIN, ENDFIN, NXFIN, and NYFIN keywords in the GRID section to fully define a Cartesian LGR grid model. + See also the CARFIN, ENDFIN, NXFIN, and NYFIN keywords in the GRID section to fully define a Cartesian LGR grid model. Example -- -- CARFIN LGR GRID COMMANDS diff --git a/parts/chapters/subsections/6.3/OPERATE.fodt b/parts/chapters/subsections/6.3/OPERATE.fodt index 804bac0a..629ec3dc 100644 --- a/parts/chapters/subsections/6.3/OPERATE.fodt +++ b/parts/chapters/subsections/6.3/OPERATE.fodt @@ -4627,7 +4627,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -5508,7 +5508,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - OPERATE Keyword and Variable Options by Section + OPERATE Keyword and Variable Options by Section @@ -5681,7 +5681,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTX + MULTX DIFFY @@ -5704,7 +5704,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTY + MULTY DIFFZ @@ -5727,7 +5727,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTZ + MULTZ TRANR @@ -6095,11 +6095,11 @@ Updated with AFR/TSA Rev-D comments and new keywords. - Table 6.95: OPERATE Keyword Applicable Arrays by Section + Table 6.95: OPERATE Keyword Applicable Arrays by Section - Note that care should be exercised when performing operations on integer array data as all transforms are performed using floating point arithmetic operations. In addition, operations on any of the transmissibility arrays (TRANX, TRANX-, TRANY, TRANY-, TRANZ, and TRANZ-) may result in untended consequences as these arrays have zero values on the boundary of the grid. The OPERATE keyword in OPM Flow uses SI units. Operations where PERMX, PERMY and PERMZ keywords are the output array, and the system of units is set to FIELD or LAB, will need to be corrected by multiplying by a conversion factor of 9.87E-16. This is not necessary with the commercial simulator. In this use OPM ResInsight to verify and visually inspect the results. + Note that care should be exercised when performing operations on integer array data as all transforms are performed using floating point arithmetic operations. In addition, operations on any of the transmissibility arrays (TRANX, TRANX-, TRANY, TRANY-, TRANZ, and TRANZ-) may result in untended consequences as these arrays have zero values on the boundary of the grid. The OPERATE keyword in OPM Flow uses SI units. Operations where PERMX, PERMY and PERMZ keywords are the output array, and the system of units is set to FIELD or LAB, will need to be corrected by multiplying by a conversion factor of 9.87E-16. This is not necessary with the commercial simulator. In this use OPM ResInsight to verify and visually inspect the results. 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). + 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). -- -- MATHEMATICAL OPERATIONS ON ARRAYS BY CELL -- diff --git a/parts/chapters/subsections/6.3/OPERATER.fodt b/parts/chapters/subsections/6.3/OPERATER.fodt index 9e721458..5c7ffbec 100644 --- a/parts/chapters/subsections/6.3/OPERATER.fodt +++ b/parts/chapters/subsections/6.3/OPERATER.fodt @@ -4652,7 +4652,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4700,7 +4700,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. 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. + Note also the OPERNUM keyword must precede the use of the OPERATER keyword. @@ -5438,7 +5438,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.ARRAY - 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. + 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. @@ -5475,7 +5475,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - OPERATER Keyword and Variable Options by Section + OPERATER Keyword and Variable Options by Section @@ -5648,7 +5648,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTX + MULTX DIFFY @@ -5671,7 +5671,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTY + MULTY DIFFZ @@ -5694,7 +5694,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - MULTZ + MULTZ TRANR @@ -6062,7 +6062,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. - Table 6.97: OPERATER Keyword Applicable Arrays by Section + Table 6.97: OPERATER Keyword Applicable Arrays by Section Note that care should be exercised when performing operations on integer array data as all transforms are performed using floating point arithmetic operations. In addition, operations on any of the transmissibility arrays (TRANX, TRANX-, TRANY, TRANY-, TRANZ, and TRANZ-) may result in unintended consequences as these arrays have zero values on the boundary of the grid. In this use OPM ResInsight to verify and visually inspect the results. @@ -6071,14 +6071,14 @@ Updated with AFR/TSA Rev-D comments and new keywords. Note - The OPERATER and OPERATE keywords allow for great flexibility in generating or modifying the simulator’s input arrays. In addition, OPM Flow also has a Python facility to manipulate and calculate data that offers even greater flexibility, but note that this feature is not compatible with the commercial simulator. + The OPERATER and OPERATE keywords allow for great flexibility in generating or modifying the simulator’s input arrays. In addition, OPM Flow also has a Python facility to manipulate and calculate data that offers even greater flexibility, but note that this feature is not compatible with the commercial simulator. Finally, OPM ResInsight, the post-processing plotting software, has both Octave and Python scripting facilities that enable both data generation and visual inspection of the results. The resulting calculated arrays can then be exported from OPM ResInsight and “included” back into OPM Flow, thus maintaining compatibility with the commercial simulator. 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. + 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. -- -- MATHEMATICAL OPERATIONS ON ARRAYS BY REGION -- diff --git a/parts/chapters/subsections/6.3/OPERNUM.fodt b/parts/chapters/subsections/6.3/OPERNUM.fodt index 22ae04b1..5c0fac8f 100644 --- a/parts/chapters/subsections/6.3/OPERNUM.fodt +++ b/parts/chapters/subsections/6.3/OPERNUM.fodt @@ -4230,7 +4230,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. @@ -4260,7 +4260,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. 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. + Note that the default value of zero implies that the calculations requested by the OPERATER keyword will not be performed. 0 @@ -4271,7 +4271,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4293,7 +4293,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 / - Alternatively the EQUALS keyword could be employed to accomplish the same task, that is: + Alternatively the EQUALS keyword could be employed to accomplish the same task, that is: -- -- ARRAY CONSTANT ---------- BOX --------- -- I1 I2 J1 J2 K1 K2 diff --git a/parts/chapters/subsections/6.3/PERMJFUN.fodt b/parts/chapters/subsections/6.3/PERMJFUN.fodt index 5e183ae3..684ff33c 100644 --- a/parts/chapters/subsections/6.3/PERMJFUN.fodt +++ b/parts/chapters/subsections/6.3/PERMJFUN.fodt @@ -4310,7 +4310,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/PERMR.fodt b/parts/chapters/subsections/6.3/PERMR.fodt index f560243e..2611cbbd 100644 --- a/parts/chapters/subsections/6.3/PERMR.fodt +++ b/parts/chapters/subsections/6.3/PERMR.fodt @@ -4312,7 +4312,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/PERMTHT.fodt b/parts/chapters/subsections/6.3/PERMTHT.fodt index 37d4a1e4..ab6e9f2a 100644 --- a/parts/chapters/subsections/6.3/PERMTHT.fodt +++ b/parts/chapters/subsections/6.3/PERMTHT.fodt @@ -4293,7 +4293,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/PERMX.fodt b/parts/chapters/subsections/6.3/PERMX.fodt index f14d967f..5e6b5ee9 100644 --- a/parts/chapters/subsections/6.3/PERMX.fodt +++ b/parts/chapters/subsections/6.3/PERMX.fodt @@ -4299,7 +4299,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/PERMY.fodt b/parts/chapters/subsections/6.3/PERMY.fodt index 2f6367cf..e5efc862 100644 --- a/parts/chapters/subsections/6.3/PERMY.fodt +++ b/parts/chapters/subsections/6.3/PERMY.fodt @@ -4296,7 +4296,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/PERMZ.fodt b/parts/chapters/subsections/6.3/PERMZ.fodt index 72a4c445..50fc2ef5 100644 --- a/parts/chapters/subsections/6.3/PERMZ.fodt +++ b/parts/chapters/subsections/6.3/PERMZ.fodt @@ -4332,7 +4332,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4391,7 +4391,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.PERMZ 0.10000 1* 1* 1* 1* 1* 1* / PERMZ * 0.1 / - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/PINCH.fodt b/parts/chapters/subsections/6.3/PINCH.fodt index 27174783..a241f696 100644 --- a/parts/chapters/subsections/6.3/PINCH.fodt +++ b/parts/chapters/subsections/6.3/PINCH.fodt @@ -4619,13 +4619,13 @@ Updated with AFR/TSA Rev-D comments and new keywords.PINCHMUL - 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: + 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. + 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. diff --git a/parts/chapters/subsections/6.3/PINCHNUM.fodt b/parts/chapters/subsections/6.3/PINCHNUM.fodt index 79b5fa99..512d66c0 100644 --- a/parts/chapters/subsections/6.3/PINCHNUM.fodt +++ b/parts/chapters/subsections/6.3/PINCHNUM.fodt @@ -4277,7 +4277,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/PINCHREG.fodt b/parts/chapters/subsections/6.3/PINCHREG.fodt index bf9207e2..7f98e8bf 100644 --- a/parts/chapters/subsections/6.3/PINCHREG.fodt +++ b/parts/chapters/subsections/6.3/PINCHREG.fodt @@ -4522,13 +4522,13 @@ Updated with AFR/TSA Rev-D comments and new keywords.PINCHMUL - 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: + 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. + 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. diff --git a/parts/chapters/subsections/6.3/PORO.fodt b/parts/chapters/subsections/6.3/PORO.fodt index 33f6f7d1..9648ce2c 100644 --- a/parts/chapters/subsections/6.3/PORO.fodt +++ b/parts/chapters/subsections/6.3/PORO.fodt @@ -4296,7 +4296,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/PYEND.fodt b/parts/chapters/subsections/6.3/PYEND.fodt index cd738c05..4b1d96bf 100644 --- a/parts/chapters/subsections/6.3/PYEND.fodt +++ b/parts/chapters/subsections/6.3/PYEND.fodt @@ -4125,19 +4125,19 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. - PYINPUT declares the start of a PYINPUT Definition Section on a single separate line, which is then followed by various standard Python commands, with one command per line. A PYINPUT Definition Section is terminated by a PYEND keyword (this keyword) on a separate single line. + 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. + PYINPUT declares the start of a PYINPUT Definition Section on a single separate line, which is then followed by various standard Python commands, with one command per line. A PYINPUT Definition Section is terminated by a PYEND keyword (this keyword) on a separate single line. There is no data required for this keyword and there is no terminating “/” for this keyword. - Although this keyword is read by OPM Flow and the script processing has been implemented, one should use caution when using this facility as it may result in OPM Flow aborting. This is because the PYINPUT facility allows the user to implement complex functionality and the implementation is new for the 2020-04 release. Users should therefore use caution when using this facility. + Although this keyword is read by OPM Flow and the script processing has been implemented, one should use caution when using this facility as it may result in OPM Flow aborting. This is because the PYINPUT facility allows the user to implement complex functionality and the implementation is new for the 2020-04 release. Users should therefore use caution when using this facility. 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. + 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. diff --git a/parts/chapters/subsections/6.3/PYINPUT.fodt b/parts/chapters/subsections/6.3/PYINPUT.fodt index daefb17d..ae05b4b0 100644 --- a/parts/chapters/subsections/6.3/PYINPUT.fodt +++ b/parts/chapters/subsections/6.3/PYINPUT.fodt @@ -4284,19 +4284,19 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. - PYINPUT declares the start of a PYINPUT Definition Section on a single separate line, which is then followed by various standard Python commands, with one command per line. A PYINPUT Definition Section is terminated by a PYEND keyword on a separate single line. + 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. + PYINPUT declares the start of a PYINPUT Definition Section on a single separate line, which is then followed by various standard Python commands, with one command per line. A PYINPUT Definition Section is terminated by a PYEND keyword on a separate single line. There is no data required for this keyword and there is no terminating “/” for this keyword. - Although this keyword is read by OPM Flow and the script processing has been implemented, one should use caution when using this facility as it may result in OPM Flow aborting. This is because the PYINPUT facility allows the user to implement complex functionality and the implementation is new for the 2020-04 release. Users should therefore use caution when using this facility. + Although this keyword is read by OPM Flow and the script processing has been implemented, one should use caution when using this facility as it may result in OPM Flow aborting. This is because the PYINPUT facility allows the user to implement complex functionality and the implementation is new for the 2020-04 release. Users should therefore use caution when using this facility. 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. + 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. @@ -4325,11 +4325,11 @@ Updated with AFR/TSA Rev-D comments and new keywords. - PYINPUT + PYINPUT - PYINPUT declares the start of a PYINPUT Definition Section. This is then followed by any number Python commands. + PYINPUT declares the start of a PYINPUT Definition Section. This is then followed by any number Python commands. Not Applicable @@ -4350,11 +4350,11 @@ Updated with AFR/TSA Rev-D comments and new keywords. - PYEND + PYEND - PYEND declares the end of a PYINPUT Definition Section. The Python code between PYINPUT and PYEND is read and executed, and the simulator thenreturns to reading the normal simulation input deck. + PYEND declares the end of a PYINPUT Definition Section. The Python code between PYINPUT and PYEND is read and executed, and the simulator thenreturns to reading the normal simulation input deck. @@ -4363,7 +4363,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - There is no terminating “/” for this keyword, instead the PYEND keyword terminates the keyword. + There is no terminating “/” for this keyword, instead the PYEND keyword terminates the keyword. @@ -4374,8 +4374,8 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.113: PYINPUT Keyword Description - The PYINPUT/PYEND set of keywords is a result of combining two programming languages, the interactive Python interpreter and OPM Flow’s source code language C++. When combining two languages one extends and embeds one into the other. When extending Python with C++ the functionality implemented in C++ is made available to Python applications, when embedding Python in C++ one can call Python functions from within C++. The PYINPUT/PYEND set of keywords is based on embedding a Python interpreter in the C++ OPM Flow simulator, but the Python code actually runs as part of the PYINPUT keyword is based on wrapping C++ objects in Python, that is extending Python. - The Python code in between the PYINPUT and PYEND keywords are imported during processing of the input deck and as such this implies that basic Python syntax checking is performed during reading the Python script. + The PYINPUT/PYEND set of keywords is a result of combining two programming languages, the interactive Python interpreter and OPM Flow’s source code language C++. When combining two languages one extends and embeds one into the other. When extending Python with C++ the functionality implemented in C++ is made available to Python applications, when embedding Python in C++ one can call Python functions from within C++. The PYINPUT/PYEND set of keywords is based on embedding a Python interpreter in the C++ OPM Flow simulator, but the Python code actually runs as part of the PYINPUT keyword is based on wrapping C++ objects in Python, that is extending Python. + The Python code in between the PYINPUT and PYEND keywords are imported during processing of the input deck and as such this implies that basic Python syntax checking is performed during reading the Python script. See also the PYACTION keyword in the SCHEDULE section which is also 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. 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. diff --git a/parts/chapters/subsections/6.3/QMOBIL.fodt b/parts/chapters/subsections/6.3/QMOBIL.fodt index 8d4c4b96..bcf1a2c7 100644 --- a/parts/chapters/subsections/6.3/QMOBIL.fodt +++ b/parts/chapters/subsections/6.3/QMOBIL.fodt @@ -4080,7 +4080,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. 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/6.3/REFINE.fodt b/parts/chapters/subsections/6.3/REFINE.fodt index c890e336..c94d3adb 100644 --- a/parts/chapters/subsections/6.3/REFINE.fodt +++ b/parts/chapters/subsections/6.3/REFINE.fodt @@ -4070,8 +4070,8 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. - The ENDFIN keyword is used to terminate the LGR definition. + 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. + The ENDFIN keyword is used to terminate the LGR definition. There is no data required for this keyword. 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/6.3/SKIP.fodt b/parts/chapters/subsections/6.3/SKIP.fodt index f1b99d59..101deab9 100644 --- a/parts/chapters/subsections/6.3/SKIP.fodt +++ b/parts/chapters/subsections/6.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/6.3/SKIP100.fodt b/parts/chapters/subsections/6.3/SKIP100.fodt index 83115fd6..a525a175 100644 --- a/parts/chapters/subsections/6.3/SKIP100.fodt +++ b/parts/chapters/subsections/6.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/6.3/SKIP300.fodt b/parts/chapters/subsections/6.3/SKIP300.fodt index c6659267..7c545852 100644 --- a/parts/chapters/subsections/6.3/SKIP300.fodt +++ b/parts/chapters/subsections/6.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/6.3/SMULTX.fodt b/parts/chapters/subsections/6.3/SMULTX.fodt index 970fd4ed..78cab581 100644 --- a/parts/chapters/subsections/6.3/SMULTX.fodt +++ b/parts/chapters/subsections/6.3/SMULTX.fodt @@ -4235,7 +4235,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description 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. - An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the SMULTX keyword to set the multipliers just for the area defined by the BOX keyword (see the example). + An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the SMULTX keyword to set the multipliers just for the area defined by the BOX keyword (see the example). This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. @@ -4276,7 +4276,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4290,7 +4290,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.118: SMULTX Keyword Description - See also the MULTX, MULTY and MULTZ keywords for scaling transmissible between grid cells. + See also the MULTX, MULTY and MULTZ keywords for scaling transmissible between grid cells. Example -- -- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS @@ -4309,7 +4309,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/SMULTY.fodt b/parts/chapters/subsections/6.3/SMULTY.fodt index 9eb3e0a7..d92fcbe2 100644 --- a/parts/chapters/subsections/6.3/SMULTY.fodt +++ b/parts/chapters/subsections/6.3/SMULTY.fodt @@ -4232,7 +4232,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description 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. - An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the SMULTY keyword to set the multipliers just for the area defined by the BOX keyword (see the example). + An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the SMULTY keyword to set the multipliers just for the area defined by the BOX keyword (see the example). This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. @@ -4273,7 +4273,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4287,7 +4287,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.119: SMULTY Keyword Description - See also the MULTX, MULTY and MULTZ keywords for scaling transmissible between grid cells. + See also the MULTX, MULTY and MULTZ keywords for scaling transmissible between grid cells. Example -- -- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS @@ -4306,7 +4306,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/SMULTZ.fodt b/parts/chapters/subsections/6.3/SMULTZ.fodt index c6113a85..e7d88dc7 100644 --- a/parts/chapters/subsections/6.3/SMULTZ.fodt +++ b/parts/chapters/subsections/6.3/SMULTZ.fodt @@ -4235,7 +4235,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description 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. - An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the SMULTZ keyword to set the multipliers just for the area defined by the BOX keyword (see the example). + An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the SMULTZ keyword to set the multipliers just for the area defined by the BOX keyword (see the example). This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. @@ -4276,7 +4276,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. @@ -4290,7 +4290,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Table 6.120: SMULTX Keyword Description - See also the MULTX, MULTY and MULTZ keywords for scaling transmissible between grid cells. + See also the MULTX, MULTY and MULTZ keywords for scaling transmissible between grid cells. Example -- -- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS @@ -4309,7 +4309,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.-- ENDBOX - The 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. + The 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. diff --git a/parts/chapters/subsections/6.3/THCGAS.fodt b/parts/chapters/subsections/6.3/THCGAS.fodt index 19b0529d..4de2dfb9 100644 --- a/parts/chapters/subsections/6.3/THCGAS.fodt +++ b/parts/chapters/subsections/6.3/THCGAS.fodt @@ -4337,7 +4337,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/THCOIL.fodt b/parts/chapters/subsections/6.3/THCOIL.fodt index 9b059221..1d09d175 100644 --- a/parts/chapters/subsections/6.3/THCOIL.fodt +++ b/parts/chapters/subsections/6.3/THCOIL.fodt @@ -4316,7 +4316,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/THCONR.fodt b/parts/chapters/subsections/6.3/THCONR.fodt index 70ba59ba..446de03c 100644 --- a/parts/chapters/subsections/6.3/THCONR.fodt +++ b/parts/chapters/subsections/6.3/THCONR.fodt @@ -4279,7 +4279,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/THCONSF.fodt b/parts/chapters/subsections/6.3/THCONSF.fodt index 404028d6..2ec887fd 100644 --- a/parts/chapters/subsections/6.3/THCONSF.fodt +++ b/parts/chapters/subsections/6.3/THCONSF.fodt @@ -4312,7 +4312,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/THCROCK.fodt b/parts/chapters/subsections/6.3/THCROCK.fodt index d7da06c6..fc11d35d 100644 --- a/parts/chapters/subsections/6.3/THCROCK.fodt +++ b/parts/chapters/subsections/6.3/THCROCK.fodt @@ -4316,7 +4316,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/THCWATER.fodt b/parts/chapters/subsections/6.3/THCWATER.fodt index 29157398..27ff2695 100644 --- a/parts/chapters/subsections/6.3/THCWATER.fodt +++ b/parts/chapters/subsections/6.3/THCWATER.fodt @@ -4313,7 +4313,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.Notes: - The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. + The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword in the RUNSPEC section, unless the BOX keyword defines a sub area of the grid, in which case the total number of entries should correspond to the number of cells defined by the BOX statement. The keyword is terminated by a “/”. diff --git a/parts/chapters/subsections/6.3/VEFIN.fodt b/parts/chapters/subsections/6.3/VEFIN.fodt index 7b760679..3398542f 100644 --- a/parts/chapters/subsections/6.3/VEFIN.fodt +++ b/parts/chapters/subsections/6.3/VEFIN.fodt @@ -4073,7 +4073,7 @@ Updated with AFR/TSA Rev-D comments and new keywords. Description - 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. + 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. 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/6.3/WARN.fodt b/parts/chapters/subsections/6.3/WARN.fodt index 1edffe3a..26a2eee7 100644 --- a/parts/chapters/subsections/6.3/WARN.fodt +++ b/parts/chapters/subsections/6.3/WARN.fodt @@ -4014,7 +4014,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.