Skip to content

Commit

Permalink
Merge pull request #218 from pkirkham/edits-3
Browse files Browse the repository at this point in the history
Typos and minor edits #3
  • Loading branch information
blattms authored Apr 12, 2024
2 parents a025b30 + 04539ee commit 70676d4
Show file tree
Hide file tree
Showing 38 changed files with 126 additions and 126 deletions.
12 changes: 6 additions & 6 deletions parts/chapters/subsections/12.3/ACTIONX.fodt
Original file line number Diff line number Diff line change
Expand Up @@ -4950,7 +4950,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.</dc:description><meta:init
<text:p text:style-name="P4986">ACTTEST</text:p>
</table:table-cell>
<table:table-cell table:style-name="Table840.C15" table:number-columns-spanned="3" office:value-type="string">
<text:p text:style-name="P5012">ACTTEST is a defined character string that the states the Boolean operator and must be set to one of the following Boolean conditionals: </text:p>
<text:p text:style-name="P5012">ACTTEST is a defined character string that states the Boolean operator and must be set to one of the following Boolean conditionals: </text:p>
<text:list xml:id="list105919889445580" text:continue-list="list105920754085367" text:style-name="_40_NumberedListTable">
<text:list-item text:start-value="1">
<text:p text:style-name="P19299">&gt;: Greater than.</text:p>
Expand All @@ -4965,7 +4965,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.</dc:description><meta:init
<text:p text:style-name="P19305">&lt;=: Less than or equal to.</text:p>
</text:list-item>
<text:list-item>
<text:p text:style-name="P19305">=: Equals to.</text:p>
<text:p text:style-name="P19305">=: Equal to.</text:p>
</text:list-item>
<text:list-item>
<text:p text:style-name="P19299">!=: Not equal to </text:p>
Expand Down Expand Up @@ -5000,7 +5000,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.</dc:description><meta:init
<text:p text:style-name="P14325">ACTIONX</text:p>
<text:p text:style-name="P14325"><text:s text:c="5"/>MXWATER <text:s text:c="5"/>10000 <text:s text:c="10"/>/</text:p>
<text:p text:style-name="P14325"><text:s text:c="5"/>GWPR <text:s/>&apos;FIELD&apos; &gt; 60E3 <text:s/>AND <text:s text:c="3"/>/</text:p>
<text:p text:style-name="P14325"><text:s text:c="5"/>WCUT ‘OP*’ <text:s/>&gt; 0.90 <text:s text:c="8"/>/</text:p>
<text:p text:style-name="P14325"><text:s text:c="5"/>WWCT ‘OP*’ <text:s/>&gt; 0.90 <text:s text:c="8"/>/</text:p>
<text:p text:style-name="P14325">/</text:p>
<text:p text:style-name="P14325">-- WELL PRODUCTION STATUS <text:s text:c="54"/></text:p>
<text:p text:style-name="P14325">-- <text:s text:c="77"/></text:p>
Expand Down Expand Up @@ -5270,7 +5270,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.</dc:description><meta:init
<text:p text:style-name="P2281">For example, </text:p>
<text:p text:style-name="P14390">ACTIONX</text:p>
<text:p text:style-name="P14390"><text:s text:c="5"/>WIPHASE <text:s text:c="6"/>1 <text:s text:c="14"/>/</text:p>
<text:p text:style-name="P14390"><text:s text:c="5"/>RRP 0 &lt; 2500 <text:s text:c="9"/><text:s text:c="8"/>/</text:p>
<text:p text:style-name="P14390"><text:s text:c="5"/>RPR 0 &lt; 2500 <text:s text:c="9"/><text:s text:c="8"/>/</text:p>
<text:p text:style-name="P14390">/</text:p>
<text:p text:style-name="P14390">…...</text:p>
<text:p text:style-name="P10152"><text:s text:c="7"/>ENDACTIO</text:p>
Expand Down Expand Up @@ -5422,7 +5422,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.</dc:description><meta:init
</table:table>
<text:p text:style-name="P14560">Table <text:sequence text:ref-name="refTable549" text:name="Table" text:formula="ooow:Table+1" style:num-format="1">12.7</text:sequence>: ACTIONX Variable Definitions</text:p>
<text:p text:style-name="P12403"/>
<text:p text:style-name="P12404">See also the ACTDIMS and UDADIMS keyword in the RUNSPEC section to define the dimensions for the ACTIONX keyword and associated variables. In addition, the EXIT keyword in the SCHEDULE section that allows for terminating the simulation for when a condition within an ACTIONX definition is satisfied</text:p>
<text:p text:style-name="P12404">See also the ACTDIMS and UDADIMS keyword in the RUNSPEC section to define the dimensions for the ACTIONX keyword and associated variables. In addition, the EXIT keyword in the SCHEDULE section that allows for terminating the simulation for when a condition within an ACTIONX definition is satisfied.</text:p>
<text:p text:style-name="P12404">Although most SCHEDULE keywords should work with the ACTIONX keyword, <text:sequence-ref text:reference-format="category-and-value" text:ref-name="refTable550">Table 12.8</text:sequence-ref><text:s/>shows the status of keywords that have been tested and known to work, together with keywords that are currently planned to be implemented.</text:p>
<table:table table:name="Table1994" table:style-name="Table1994">
<table:table-column table:style-name="Table1994.A" table:number-columns-repeated="6"/>
Expand Down Expand Up @@ -5793,7 +5793,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.</dc:description><meta:init
</table:table-header-rows>
</table:table>
<text:p text:style-name="P12405"/>
<text:p text:style-name="P11825">User Defined Quantities and also be used as User Defined Arguments (“UDA”) in the SCHEDULE section with various group, well, and connection keywords. In this case, the UDA variables are used to replace numerical values on these keywords by UDA variables that have been defined by the UDQ keyword. <text:s/>For example, if we wish to make the oil rate for certain wells to be a function of their water cut, then one can define the function using the UDQ keyword that results in a UDQ variable, WU_WCUT say, and then use WU_WCUT as a UDA variable on the WCONPROD keyword for the ORAT parameter. <text:s/>See <text:s/><text:sequence-ref text:reference-format="category-and-value" text:ref-name="refTable614">Table 12.72</text:sequence-ref><text:s/>for a list of keywords that can be used with UDA variables in the <text:a xlink:type="simple" xlink:href="#12.3.59.UDQ - Declare User Define Quantities (“UDQ”)|outline" text:style-name="Internet_20_link" text:visited-style-name="Visited_20_Internet_20_Link"><text:bookmark-ref text:reference-format="text" text:ref-name="__RefHeading___Toc161095_2932703077">UDQ - Declare User Define Quantities (“UDQ”)</text:bookmark-ref></text:a><text:s/>keyword section.</text:p>
<text:p text:style-name="P11825">User Defined Quantities can also be used as User Defined Arguments (“UDA”) in the SCHEDULE section with various group, well, and connection keywords. In this case, the UDA variables are used to replace numerical values on these keywords by UDA variables that have been defined by the UDQ keyword. <text:s/>For example, if we wish to make the oil rate for certain wells to be a function of their water cut, then one can define the function using the UDQ keyword that results in a UDQ variable, WU_WCUT say, and then use WU_WCUT as a UDA variable on the WCONPROD keyword for the ORAT parameter. <text:s/>See <text:s/><text:sequence-ref text:reference-format="category-and-value" text:ref-name="refTable614">Table 12.72</text:sequence-ref><text:s/>for a list of keywords that can be used with UDA variables in the <text:a xlink:type="simple" xlink:href="#12.3.59.UDQ - Declare User Define Quantities (“UDQ”)|outline" text:style-name="Internet_20_link" text:visited-style-name="Visited_20_Internet_20_Link"><text:bookmark-ref text:reference-format="text" text:ref-name="__RefHeading___Toc161095_2932703077">UDQ - Declare User Define Quantities (“UDQ”)</text:bookmark-ref></text:a><text:s/>keyword section.</text:p>
<text:h text:style-name="Heading_20_4" text:outline-level="4"><text:bookmark-start text:name="__RefHeading___Toc716521_3964674244"/><text:span text:style-name="T1">Example</text:span>s<text:bookmark-end text:name="__RefHeading___Toc716521_3964674244"/></text:h>
<text:p text:style-name="_40_TextBody">The first example uses the UDQ keyword to sort the oil wells from high water cut to low, via the WU_WLIST variable, and then use the ACTIONX keyword to shut-in the worst offending well when the field’s water production is greater than 30,000 stb/d.</text:p>
<text:p text:style-name="P12904">--</text:p>
Expand Down
4 changes: 2 additions & 2 deletions parts/chapters/subsections/12.3/COMPSEGS.fodt
Original file line number Diff line number Diff line change
Expand Up @@ -4441,7 +4441,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.</dc:description><meta:init
</table:table-row>
</table:table>
<text:h text:style-name="P18345" text:outline-level="4" text:is-list-header="true"><text:bookmark-start text:name="__RefHeading___Toc716555_3964674244"/>Description<text:bookmark-end text:name="__RefHeading___Toc716555_3964674244"/></text:h>
<text:p text:style-name="_40_TextBody">The COMSEGS keyword defines how a multi-segment well is connected to the reservoir by defining or modifying existing well connections. Note that well must have been previously define by the WELSPECS keyword in the SCHEDULE section and the well connections must have been previously defined via the COMPDAT keyword in the SCHEDULE section </text:p>
<text:p text:style-name="_40_TextBody">The COMSEGS keyword defines how a multi-segment well is connected to the reservoir by defining or modifying existing well connections. Note that well must have been previously define by the WELSPECS keyword in the SCHEDULE section and the well connections must have been previously defined via the COMPDAT keyword in the SCHEDULE section.</text:p>
<text:p text:style-name="_40_TextBody">The COMPSEGS keyword should be repeated for each multi-segment well in the model. <text:s/></text:p>
<table:table table:name="Table1002" table:style-name="Table1002">
<table:table-column table:style-name="Table1002.A"/>
Expand Down Expand Up @@ -4826,7 +4826,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.</dc:description><meta:init
<text:p text:style-name="P14654">Table <text:sequence text:ref-name="refTable559" text:name="Table" text:formula="ooow:Table+1" style:num-format="1">12.17</text:sequence>: COMPSEGS Keyword Description</text:p>
<text:p text:style-name="_40_TextBody"/>
<text:p text:style-name="P11522">The total number of wells and completions should be defined via the WELLSDIMS keyword and the number of multi-segment wells and completions should be declared on the WSEGDIMS keyword, both keywords are in the RUNSPEC section. </text:p>
<text:p text:style-name="P11336">See also the WELSPECS keyword to define wells, the COMPDAT keyword to define the well connections for both ordinary wells and multi-segment wells, and the COMPSEGL keyword to define a multi-segment <text:s/>connections in a LGR. All the aforementioned keywords are described in the SCHEDULE section. </text:p>
<text:p text:style-name="P11336">See also the WELSPECS keyword to define wells, the COMPDAT keyword to define the well connections for both ordinary wells and multi-segment wells, and the COMPSEGL keyword to define multi-segment <text:s/>connections in a LGR. All the aforementioned keywords are described in the SCHEDULE section. </text:p>
<text:h text:style-name="P18558" text:outline-level="4"><text:bookmark-start text:name="__RefHeading___Toc716557_3964674244"/>Example<text:bookmark-end text:name="__RefHeading___Toc716557_3964674244"/></text:h>
<text:p text:style-name="P11336">The following example defines the completions for two oil producing segment oil wells (OP01 and OP02) using the COMPSEGS keywords. <text:s text:c="3"/></text:p>
<text:p text:style-name="P14135">-- <text:s text:c="6"/>COMPLETION SEGMENT SPECIFICATION DATA <text:s text:c="52"/></text:p>
Expand Down
2 changes: 1 addition & 1 deletion parts/chapters/subsections/12.3/COMPTRAJ.fodt
Original file line number Diff line number Diff line change
Expand Up @@ -5009,7 +5009,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.</dc:description><meta:init
<text:p text:style-name="P107">TOP</text:p>
</table:table-cell>
<table:table-cell table:style-name="Table2266.C2" table:number-columns-spanned="3" office:value-type="string">
<text:p text:style-name="P107">A real positive value that defines depth of top of the perforation interval, and should be less than the value entered for the BOT parameter (the bottom perforation depth).</text:p>
<text:p text:style-name="P107">A real positive value that defines the depth of the top of the perforation interval, and should be less than the value entered for the BOT parameter (the bottom perforation depth).</text:p>
</table:table-cell>
<table:covered-table-cell/>
<table:covered-table-cell/>
Expand Down
4 changes: 2 additions & 2 deletions parts/chapters/subsections/12.3/DRSDT.fodt
Original file line number Diff line number Diff line change
Expand Up @@ -4375,7 +4375,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.</dc:description><meta:init
<text:p text:style-name="P14709">Table <text:sequence text:ref-name="refTable562" text:name="Table" text:formula="ooow:Table+1" style:num-format="1">12.20</text:sequence>: DRSDT Keyword Description</text:p>
<text:p text:style-name="P15537"/>
<text:p text:style-name="_40_TextBody">Note this keyword can be used in history matching field performance to control the availability of the movable gas phase.</text:p>
<text:p text:style-name="_40_TextBody"><text:soft-page-break/>See also the VAPPAR keyword in the SOLUTION section and the DRSDTR, DRVDT and DRVDTR keywords in the SCHEDULE section that controls how vaporized oil is treated and the rate at which the dissolved phase ratio increases within a grid block.</text:p>
<text:p text:style-name="_40_TextBody"><text:soft-page-break/>See also the VAPPARS keyword in the SOLUTION section and the DRSDTR, DRVDT and DRVDTR keywords in the SCHEDULE section that controls how vaporized oil is treated and the rate at which the dissolved phase ratio increases within a grid block.</text:p>
<text:p text:style-name="_40_TextBody"/>
<text:h text:style-name="P18728" text:outline-level="4"><text:bookmark-start text:name="__RefHeading___Toc716561_3964674244"/>Examples<text:bookmark-end text:name="__RefHeading___Toc716561_3964674244"/></text:h>
<text:p text:style-name="P11526">The first example prevents the solution gas-oil ratio from increasing and applies this to all grid cells.</text:p>
Expand All @@ -4387,7 +4387,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.</dc:description><meta:init
<text:p text:style-name="P14085">-- <text:s text:c="6"/>------- <text:s text:c="2"/>-------- <text:s text:c="41"/></text:p>
<text:p text:style-name="P13099"><text:s text:c="9"/>0.000 <text:s text:c="4"/>ALL <text:s text:c="36"/>/ <text:s text:c="76"/></text:p>
<text:p text:style-name="P15084"/>
<text:p text:style-name="P15480">And the second example below applies 0.005 Mscf/stb/d as the maximum rate at which the solution gas-oil ratio is allowed to increase in a grid cell, and applies this to only cells containing free gas.</text:p>
<text:p text:style-name="P15480">And the second example below applies 0.0005 Mscf/stb/d as the maximum rate at which the solution gas-oil ratio is allowed to increase in a grid cell, and applies this to only cells containing free gas.</text:p>
<text:p text:style-name="P14086">-- <text:s text:c="84"/></text:p>
<text:p text:style-name="P14086">-- <text:s text:c="6"/>SOLUTION GAS (RS) MAXIMUM RATE OF INCREASE FOR MODEL <text:s text:c="43"/>-- <text:s text:c="3"/></text:p>
<text:p text:style-name="P14086">DRSDT</text:p>
Expand Down
4 changes: 2 additions & 2 deletions parts/chapters/subsections/12.3/DRSDTR.fodt
Original file line number Diff line number Diff line change
Expand Up @@ -4383,7 +4383,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.</dc:description><meta:init
<text:p text:style-name="P14710">Table <text:sequence text:ref-name="refTable564" text:name="Table" text:formula="ooow:Table+1" style:num-format="1">12.22</text:sequence>: DRSDTR Keyword Description</text:p>
<text:p text:style-name="P15538"/>
<text:p text:style-name="_40_TextBody">Note this keyword can be used in history matching field performance to control the availability of the movable gas phase.</text:p>
<text:p text:style-name="_40_TextBody">See also the VAPPAR keyword in the SOLUTION section and the DRSDT, DRVDT and DRVDTR keywords in the SCHEDULE section that controls how vaporized oil is treated and the rate at which the dissolved phase ratio increases within a grid block.</text:p>
<text:p text:style-name="_40_TextBody">See also the VAPPARS keyword in the SOLUTION section and the DRSDT, DRVDT and DRVDTR keywords in the SCHEDULE section that controls how vaporized oil is treated and the rate at which the dissolved phase ratio increases within a grid block.</text:p>
<text:p text:style-name="_40_TextBody">This keyword is not supported by OPM Flow but has no effect on the results so it will be ignored but is documented here for completeness, as it is expected to be available in the next release of OPM Flow.</text:p>
<text:h text:style-name="P18563" text:outline-level="4"><text:bookmark-start text:name="__RefHeading___Toc716565_3964674244"/>Examples<text:bookmark-end text:name="__RefHeading___Toc716565_3964674244"/></text:h>
<text:p text:style-name="P11527">The first example prevents the solution gas-oil ratio from increasing and applies this to all regions for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.</text:p>
Expand All @@ -4397,7 +4397,7 @@ Updated with AFR/TSA Rev-D comments and new keywords.</dc:description><meta:init
<text:p text:style-name="P13101"><text:s text:c="9"/>0.0000 <text:s text:c="3"/>ALL <text:s text:c="36"/>/ <text:s text:c="76"/></text:p>
<text:p text:style-name="P13101"><text:s text:c="9"/>0.0000 <text:s text:c="3"/>ALL <text:s text:c="36"/>/ <text:s text:c="76"/></text:p>
<text:p text:style-name="P15073"/>
<text:p text:style-name="_40_TextBody">The second example below prevents the solution gas-oil ratio from increasing and applies this to all grid cells in PVTNUM region one. For PVTNUM regions one and two the keyword applies 0.005 Mscf/stb/d as the maximum rate at which the solution gas-oil ratio is allowed to increase in a grid cell, and applies this to only cells containing free gas.</text:p>
<text:p text:style-name="_40_TextBody">The second example below prevents the solution gas-oil ratio from increasing and applies this to all grid cells in PVTNUM region one. For PVTNUM regions one and two the keyword applies 0.0005 Mscf/stb/d as the maximum rate at which the solution gas-oil ratio is allowed to increase in a grid cell, and applies this to only cells containing free gas.</text:p>
<text:p text:style-name="P14087">-- <text:s text:c="84"/></text:p>
<text:p text:style-name="P14088">-- <text:s text:c="6"/>SOLUTION GAS (RS) MAXIMUM RATE OF INCREASE BY REGION <text:s text:c="43"/>-- <text:s text:c="3"/></text:p>
<text:p text:style-name="P14087">DRSDTR</text:p>
Expand Down
Loading

0 comments on commit 70676d4

Please sign in to comment.