mirror of
https://github.com/OPM/ResInsight.git
synced 2025-02-25 18:55:39 -06:00
Update GettingStarted.md
This commit is contained in:
parent
cbb4441ec0
commit
d118d0f60b
@ -1,4 +1,3 @@
|
|||||||
|
|
||||||
# Getting started with ResInsight #
|
# Getting started with ResInsight #
|
||||||
|
|
||||||
## Application overview ##
|
## Application overview ##
|
||||||
@ -18,16 +17,20 @@ the **Restore down** icon in the application show here for Windows :
|
|||||||
|
|
||||||

|

|
||||||
|
|
||||||
### Project Tree ###
|
Toggling a checkbox next to an item in the **Project Tree** will toggle visibility in the 3D view. Toggling a checkbox for a collection of items will toggle visibility for all items in the collection.
|
||||||
Grid Models contains Eclipse cases organized in the following structure
|
|
||||||
|
|
||||||
-  Binary case created from .EGRID or .GRID file
|
### Input data support ###
|
||||||
-  Binary case created from .EGRID or .GRID file
|
ResInsight supports the follwing type of Eclipse input data
|
||||||
-  Input cases created from .GRDECL file
|
|
||||||
-  A Grid Case Group can be created from a
|
####  Binary case
|
||||||
selection of binary files, or manually by assigning cases using the user interface of ResInsight.
|
Read grid from .EGRID or .GRID file and binary data from UNRST files.
|
||||||
|
|
||||||
|
####  Input case
|
||||||
|
Read grid from from .GRDECL file and property data from Ascii files.
|
||||||
|
|
||||||
|
####  Grid Case Group
|
||||||
|
A Grid Case Group can be created from a selection of binary files, or manually by assigning cases using the user interface of ResInsight.
|
||||||
|
|
||||||
Toggling a checkbox next to an item will toggle visibility in the 3D view. Toggling a checkbox for a collection of items will toggle visibility for all items in the collection.
|
|
||||||
|
|
||||||
## Open an Eclipse case ##
|
## Open an Eclipse case ##
|
||||||
1. Select **File->Import->Import Eclipse Case** and select Eclipse file for import
|
1. Select **File->Import->Import Eclipse Case** and select Eclipse file for import
|
||||||
@ -86,11 +89,11 @@ All filters can be controlled from the **Property Editor**.
|
|||||||
|
|
||||||
Using range filters enables the user to define a set of IJK visible regions in the 3D view. A single IJK-slice can be added from the context menu when rightclicking a grid cell. A new range filter can also be added by activating the context menu for the **Range Filters** collection in the **Project Tree**.
|
Using range filters enables the user to define a set of IJK visible regions in the 3D view. A single IJK-slice can be added from the context menu when rightclicking a grid cell. A new range filter can also be added by activating the context menu for the **Range Filters** collection in the **Project Tree**.
|
||||||
|
|
||||||
## Property filters ##
|
### Property filters ###
|
||||||
|
|
||||||
In addition to range filters, it is possible to filter visible grid cells based on a property value range. Add a new property filter by activating the context menu for **Property Filters**. The new property filter is based on currently selected cell result.
|
In addition to range filters, it is possible to filter visible grid cells based on a property value range. Add a new property filter by activating the context menu for **Property Filters**. The new property filter is based on currently selected cell result.
|
||||||
|
|
||||||
## Well range filter ##
|
### Well range filter ###
|
||||||
Select **Wells** in the **Project Tree**. In the **Property Editor**, select **On** for **Add cells to range filter**. This will hide cells not part of a well.
|
Select **Wells** in the **Project Tree**. In the **Property Editor**, select **On** for **Add cells to range filter**. This will hide cells not part of a well.
|
||||||
In addition, all cells along a direction can be added as a fence. Enable this by checking **Use well fence**.
|
In addition, all cells along a direction can be added as a fence. Enable this by checking **Use well fence**.
|
||||||
|
|
||||||
@ -123,7 +126,7 @@ Result data can be exported to Eclipse Ascii file by activating the context menu
|
|||||||
|
|
||||||
|
|
||||||
# Script interface to Octave #
|
# Script interface to Octave #
|
||||||
ResInsight provides a flexible interface to [Octave](http://www.gnu.org/software/octave/ "Octave") for scripts execution.
|
ResInsight provides a flexible interface to [Octave](http://www.gnu.org/software/octave/ "Octave") for scripts execution. ResInsight can create an external Octave process, and is able to send and receive data from this external process.
|
||||||
|
|
||||||
## Script execution - single case ##
|
## Script execution - single case ##
|
||||||
A script can be started by navigating to the script in the **Project Tree**, and selecting **Execute** from the context menu. The currently active case will be manipulated by the Octave script. It is also possible to execute a script from the context menu of a case.
|
A script can be started by navigating to the script in the **Project Tree**, and selecting **Execute** from the context menu. The currently active case will be manipulated by the Octave script. It is also possible to execute a script from the context menu of a case.
|
||||||
|
Loading…
Reference in New Issue
Block a user