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

Doc: Work in process

Browse Source
This commit is contained in:
Magne Sjaastad
2014-01-06 08:52:54 +01:00
parent 78571b0912
commit d393368df4
2 changed files with 79 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/UsersGuide/BatchCommands.md
View File

@@ -1,13 +1,13 @@
[ Contents ](UsersGuide.md#contents)
------
## Batch Commands #
## Batch Commands
ResInsight supports several commands useful in a batch setting. These examples are available from the [test section](https://github.com/OPM/ResInsight/tree/master/TestModels/Case_with_10_timesteps).
See also [ Command Line Arguments](CommandLineParameters.md) for an overview of all command line arguments.
# Example 1 : Create snapshots of all views for multiple cases
### Example 1 : Create snapshots of all views for multiple cases
A list of cases is defined in **CaseList.txt**, containing the following
Real0/BRUGGE_0000.EGRID
@@ -22,7 +22,7 @@ The command line used to run this example is shown here:
This will instruct ResInsight to read the project file **BatchTest.rsp**. All cases will be replaced one by one in ResInsight, and snapshots of all views will be written to file.
# Example 2 : Replace a single case and take snapshots of all views
### Example 2 : Replace a single case and take snapshots of all views
The command line used to run this example is shown here:
@@ -31,7 +31,7 @@ The command line used to run this example is shown here:
This will instruct ResInsight to read the project file **BatchTest.rsp**. The specified case **Real10\BRUGGE_0010.EGRID** will be imported into the project, and snapshots of all views will be written to file.
# Example 3 : Replace source cases in a case group and create snapshot
### Example 3 : Replace source cases in a case group and create snapshot
A list of cases is defined in **CaseList2.txt**, containing the following
Real0/BRUGGE_0000.EGRID

75
Documentation/UsersGuide/Faults.md Normal file
View File

@@ -0,0 +1,75 @@
[ Contents ](UsersGuide.md#contents)
-----
## Faults
ResInsight can import faults from `*.DATA` files, and is available in the Faults folder in the project view.
As import of faults can be time consuming, reading of faults can be disabled from **Preferences -> Read fault data**
### Fault imports
The command **File -> Import -> Import Well Paths From File** will read the well paths in the selected file, and create one entry for each trajectory under the ![](images/WellCollection.png) **Wells** item in the **Project Tree**.
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 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 well name is found, a new well is created and the following data points ends up in it.
###### Example 1:
WELLNAME: ‘WELL1’
4507.0 5638.5 0.0 0.0
4507 5638.5 4628.6 1628.6
4297.4 5938.5 4632.4 1998.387
-999
WELLNAME: ‘WELL2’
5507.0 4638.5 0.0 0.0
5507 4638.5 3628.6 1628.6
5297.4 4938.5 3632.4 1998.387
-999
###### Example 2:
X Y TVD MD
Name Well_1
5507.0 4638.5 0.0 0.0
5507 4638.5 3628.6 1628.6
5297.4 4938.5 3632.4 1998.387
Name Well_2
5507.0 4638.5 0.0 0.0
5507 4638.5 3628.6 1628.6
5297.4 4938.5 3632.4 1998.387
The trajectory data is not copied into the ResInsight project as such. The project file only stores the file path, and the next time you open the project, ResInsight will try to read the well data from the file again.
### Importing from SSI-Hub (Internal Statoil web-service)
The command **File -> Import -> Import Well Paths From SSI-hub** launches a wizard to guide you through the process of selecting the well trajectories you need.
After completing the wizard, the wells imported are accessible as Items under the ![](images/WellCollection.png) **Wells** item in the **Project Tree**.
The trajectory data is not copied into the ResInsight project as such, but is stored in files in a directory called <ProjectFileName>_wellpaths in the same directory as your project file.
### Well Trajectory visualization
All the imported well trajectories are available below the ![](images/WellCollection.png) **Wells** item in the **Project Tree**.
![](images/WellsInTree.png)
The visible wells are always shown in all the 3D Views in the complete project, so the toggles and settings control the overall project visibility of the Well Trajectories. The **Property Editor** of the **Wells** item is shown below
![](images/WellPathCollectionProperties.png)
- **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.
------
[ Contents ](UsersGuide.md#contents)