OilfieldToolsNet/ResInsight
4
0
Fork 0
mirror of https://github.com/OPM/ResInsight.git synced 2025-02-25 18:55:39 -06:00
Code Issues Packages Projects Releases Wiki Activity

User Doc Fixing Typos

Browse Source
This commit is contained in:
Jacob Støren 2013-10-24 14:52:49 +02:00
parent 11b9c40607
commit 312d036129
3 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/UsersGuide/CaseGroupsAndStatistics.md
View File

@ -17,7 +17,7 @@ An import dialog is opened:
1. Add one or more search folders to the list on the left.
2. The *.EGRID or *.GRID files found in these directories and sub directories are shown in the list to the right.
3. If you want to remove EGRID files from the list, select them and press the **Remove** button.
3. If you want to remove some *.EGRID files from the list, select them and press the **Remove** button.
4. When you are ready, press the **OK** button.
ResInsight then creates a **Grid Case Group** for you, and populates its **Source Cases** with the Cases you selected. Then the first of those Cases are read completely, while the others are just scanned to verify that the Grids match and to detect changes in the Active Cells layout.
@ -26,7 +26,7 @@ This makes it quite fast to lo ad even a quite large number of realizations.
#### Manually
A Grid Case Group can be created from the context menu available when right clicking a Result Case, Input Case or a different Grid Case Group. **Source Cases** can then be added by using the mouse to *drag and drop* cases with equal grids into the **Grid Case Group**'s **Sorce Case** folder.
A Grid Case Group can be created from the context menu available when right clicking a Result Case, Input Case or a different Grid Case Group. **Source Cases** can then be added by using the mouse to *drag and drop* cases with equal grids into the **Grid Case Group**'s **Source Case** folder.
This is useful if you want to create statistics based only on a subset of the source cases in an already created **Grid Case Group**.
**Drag and Drop** of cases will normally copy the cases to the new destination, but moving them is possible by pressing and holding the **Shift** key while dropping.
@ -48,7 +48,7 @@ The properties of an uncalculated and a calculated **Statistics Case** is shown
- **Edit** : Deletes the calculated results, and makes the controls to edit the setup available.
- **Summary of calculation setup** : Summarizes what to calculate
- **Properties to consider**: These options makes it possible to select what Eclipse properties to include in the Statistical calculations. Adding variables increase the memory usage and the computational time.
- **Percentile Setup**: Selects wether to calculate percentiles, what method and what percentile levels should be used. Turning this off speeds up the calculations.
- **Percentile Setup**: Selects whether to calculate percentiles, what method and what percentile levels should be used. Turning this off speeds up the calculations.
- **Well Data Source Case**: This option selects which set of **Simulation Wells** to be shown along with the statistical results. You can select one of the **Source Cases**.
>##### Percentile Methods
@ -60,7 +60,7 @@ The properties of an uncalculated and a calculated **Statistics Case** is shown
>- **Nearest Observation**
>The values are sorted, and the first observation representing a probability higher or equal to the percentile probability is selected as the value for the percentile. This method is by some considered to be statistically more puristic.
>- **Histogram based estimate**
>A histogram is created and the percentile is calculated based on the histogram. This method will be faster when having a large number of realisations, because no value sorting is involved. You would however need several hundred realisations before this method should be considered.
>A histogram is created and the percentile is calculated based on the histogram. This method will be faster when having a large number of realizations, because no value sorting is involved. You would however need several hundred realizations before this method should be considered.
>
#### Viewing the results
When the computation is complete, you have to create a 3D View on the **Statistics Case** to view the results. Use the Context menu available by right clicking the **Statistics Case** to create it.

6
Documentation/UsersGuide/RegressionTestSystem.md
View File

@ -17,7 +17,7 @@ From the ResInsight Gui select : **File->Testing->Regression Test Dialog**
![](images/RegressionTestDialog.png)
Specify location of compare tool in **Folder containing compare**. The current working directory of Resinsight is temporarily changed to this path during execution.
Specify location of compare tool in **Folder containing compare**. The current working directory of ResInsight is temporarily changed to this path during execution.
### Creating regression tests
@ -34,8 +34,8 @@ An example of the folder structure is shown below:
To create regression tests you need to do the following:
1. Create a root directory containing one directory for each testcase.
2. In each of the **Test Case** folders create a Resinsight project file called **RegressionTest.rip**.
1. Create a root directory containing one directory for each test case.
2. In each of the **Test Case** folders create a ResInsight project file called **RegressionTest.rip**.
3. Run the regression test for the first time, and thereby creating images that can be used as Base images.
4. Rename the generated RegTestGeneratedImages/ folder to RegTestBaseImages/

8
Documentation/UsersGuide/WellPaths.md
View File

@ -1,7 +1,7 @@
## Well trajectories
ResInsight can import Well trajectories from simple Ascii files.
In addition a Statoil specific solution to retreive Well Trajectories from their internal web service are implemented.
In addition a Statoil specific solution to retrieve Well Trajectories from their internal web service are implemented.
### Ascii Well Trajectories
@ -9,11 +9,11 @@ The command **File -> Import -> Import Well Paths From File** will read the well
The supported ascii format is quite flexible but the main requirements are:
1. Each data line must contain four numbers: X Y TVD MD separated with witespace.
1. Each data line must contain four numbers: X Y TVD MD separated with white-space.
2. A line starting with none-number-characters are ignored, unless :
1. If the line contains a pair of : ', `, ´, ’ or ‘ the text between the quotation marks is used as a well name.
2. If the line contains the case insensitive string "name " the rest of the line is used as a well name.
3. If a wellname is found, a new well is created and the following datapoints ends up in it.
3. If a well name is found, a new well is created and the following data points ends up in it.
###### Example 1:
@ -61,7 +61,7 @@ The visible wells are always shown in all the 3D Views in the complete project,
![](images/WellPathCollectionProperties.png)
- **Global well path visibility** This option forces the wellpaths on or off, ignoring the individual settings unless it is set to Individual.
- **Global well path visibility** This option forces the well paths on or off, ignoring the individual settings unless it is set to Individual.
- **Clip Well Paths** This option hides the top of the Well Trajectories to avoid displaying the very long lines from the reservoir to the sea surface.
- **Well Path clipping depth distance** This number is the distance from the top of the reservoir to the clipping depth.