mirror of
https://github.com/OPM/ResInsight.git
synced 2025-02-25 18:55:39 -06:00
Bulk commit of new documentation for release 2018.01
This commit is contained in:
Jacob Støren
parent
e4db9f48b1
commit
d13568b8ed
@ -10,32 +10,51 @@
|
||||
- gridimportexport
|
||||
- modelnavigation
|
||||
|
||||
- title: Application
|
||||
- title: 3D Main Window
|
||||
docs:
|
||||
- reservoirviews
|
||||
- cellresults
|
||||
- resultcolorlegend
|
||||
- resultinspection
|
||||
- gridstatisticsdialog
|
||||
- linkedviews
|
||||
- simulationwells
|
||||
- faults
|
||||
- intersections
|
||||
- filters
|
||||
- formations
|
||||
- wellpaths
|
||||
- linkedviews
|
||||
- completions
|
||||
- formations
|
||||
- casegroupsandstatistics
|
||||
- preferences
|
||||
|
||||
- title: Plot Window
|
||||
docs:
|
||||
- summaryplots
|
||||
- summaryploteditor
|
||||
- summarycrossplots
|
||||
- observeddata
|
||||
- curvecalculator
|
||||
- welllogsandplots
|
||||
- rftplot
|
||||
- pltplot
|
||||
- flowdiagnosticsplots
|
||||
- preferences
|
||||
|
||||
- title: Export and Interfaces
|
||||
|
||||
- title: Export and Import
|
||||
docs:
|
||||
- snapshots
|
||||
- batchcommands
|
||||
- exporteclipseproperties
|
||||
- octaveinterface
|
||||
- exportfluxnummultnum
|
||||
- carfinexport
|
||||
- odbsupport
|
||||
- importobstimehistdata
|
||||
- pasteexceltimedata
|
||||
|
||||
- title: Scripting
|
||||
docs:
|
||||
- octaveinterface
|
||||
- batchcommands
|
||||
- commandfile
|
||||
|
||||
- title: Appendix
|
||||
docs:
|
||||
|
||||
@ -1,16 +0,0 @@
|
||||
---
|
||||
layout: news_item
|
||||
title: "ResInsight 1.3.2 Dev Released"
|
||||
date: "2015-01-10 02:12:52 +0200"
|
||||
author: magnesj
|
||||
version: 1.3.2-dev
|
||||
categories:
|
||||
- testrelease
|
||||
---
|
||||
|
||||
## Test release including fix for selected clients
|
||||
|
||||
Added support for fault face using plus to indicate face
|
||||
|
||||
## Download
|
||||
[Release Binaries on GitHub](https://github.com/OPM/ResInsight/releases/tag/v1.3.2-dev)
|
||||
@ -1,18 +0,0 @@
|
||||
---
|
||||
layout: news_item
|
||||
title: "Flow Diagnostics Project"
|
||||
date: "2016-04-01 16:00:00 +0200"
|
||||
author: magnesj
|
||||
categories:
|
||||
- community
|
||||
---
|
||||
|
||||
We are happy to announce a new development project for ResInsight named **Flow Diagnostics**, which will be delivered to Statoil Petroleum AS in 2017.
|
||||
|
||||
The main goal of this project is to implement selected functionality of the flow diagnostics module from the **The Matlab Reservoir Simulation Toolbox – MRST** developed by SINTEF. Flow diagnostics capability will allow for interactive numerical flow experiments for probing a reservoir model, establish connections and basic volume estimates, and quickly provide a qualitative picture of the flow patterns in the reservoir.
|
||||
|
||||
In addition, plotting of curves based on data from Eclipse Summary files will be implemented.
|
||||
|
||||
See [Roadmap]({{ site.baseurl }}/project/roadmap) for more info.
|
||||
|
||||
[MRST project at SINTEF](http://www.sintef.no/projectweb/mrst/modules/diagnostics/)
|
||||
14
_posts/2018-01-05-resinsight-2018.01-released.md
Normal file
14
_posts/2018-01-05-resinsight-2018.01-released.md
Normal file
@ -0,0 +1,14 @@
|
||||
---
|
||||
layout: news_item
|
||||
title: "ResInsight 2018.01 Released"
|
||||
date: "2018-01-05 16:00:00 +0200"
|
||||
author: jacobStoren
|
||||
version: 2018.01
|
||||
categories:
|
||||
- release
|
||||
---
|
||||
We are happy to announce the release of ResInsight v2018.01
|
||||
|
||||
### Download
|
||||
Have a look at the [GitHub release-page](https://github.com/OPM/ResInsight/releases) to read the release-notes
|
||||
or download the new release from the [Download]({{site.baseurl}}/project/download) page.
|
||||
@ -8,13 +8,15 @@ published: true
|
||||
## Source code
|
||||
The source code is hosted at [GitHub](https://github.com/opm/resinsight)
|
||||
|
||||
## Dependencies and prerequisites
|
||||
In a git enabled shell do: `git clone https://github.com/OPM/ResInsight.git`
|
||||
|
||||
### Windows compiler
|
||||
## Dependencies and Prerequisites
|
||||
|
||||
### Windows Compiler
|
||||
|
||||
Visual Studio 2015 or later is supported.
|
||||
|
||||
### GCC compiler
|
||||
### GCC Compiler
|
||||
|
||||
GCC version 4.9 or later is supported. On RedHat Linux 6 you need to install devtoolset-3, and enable it with
|
||||
|
||||
@ -25,15 +27,18 @@ GCC version 4.9 or later is supported. On RedHat Linux 6 you need to install dev
|
||||
[Qt](http://download.qt.io/archive/qt/) Qt4 version 4.6.2 or later is supported. Qt5 is not supported yet.
|
||||
On Windows we recommend Qt-4.8.7, while the default installation will do under Linux.
|
||||
|
||||
You will need to patch the Qt sources in order to make them build using Visual Studion 2015 using this : [Qt-patch](https://github.com/appleseedhq/appleseed/wiki/Making-Qt-4.8.7-compile-with-Visual-Studio-2015)
|
||||
You will need to patch the Qt sources in order to make them build using Visual Studion 2015 using this :
|
||||
[Qt-patch](https://github.com/appleseedhq/appleseed/wiki/Making-Qt-4.8.7-compile-with-Visual-Studio-2015)
|
||||
|
||||
### CMake
|
||||
[CMake](https://cmake.org/download/) version 2.8 or later is supported.
|
||||
|
||||
## Build instructions
|
||||
The ResInsight build may be configured in different ways, with optional support for Octave plugins, ABAQUS ODB API, and OpenMP. This is configured using options in CMake.
|
||||
## Build Instructions
|
||||
The ResInsight build may be configured in different ways, with optional support for Octave plugins,
|
||||
ABAQUS ODB API, HDF5, and OpenMP. This is configured using options in CMake.
|
||||
|
||||
If you check the button 'Grouped' in the CMake GUI, the CMake variables are grouped by prefix. This makes it easier to see all of the options for ResInsight.
|
||||
If you check the button 'Grouped' in the CMake GUI, the CMake variables are grouped by prefix.
|
||||
This makes it easier to see all of the options for ResInsight.
|
||||
|
||||
- Open the CMake GUI
|
||||
- Set the path to the source code
|
||||
@ -44,12 +49,14 @@ If you check the button 'Grouped' in the CMake GUI, the CMake variables are grou
|
||||
- Run the compiler using the generated makefiles or solution file/project files to build ResInsight
|
||||
|
||||
### Windows
|
||||
ResInsight has been verified to build and run on Windows 7/8/10 using Microsoft Visual Studio 2015. Typical usage on Windows is to follow the build instructions above, and then open the generated solution file in Visual Studio to build the application.
|
||||
ResInsight has been verified to build and run on Windows 7/8/10 using Microsoft Visual Studio 2015/2017.
|
||||
Typical usage on Windows is to follow the build instructions above, and then open the generated
|
||||
solution file in Visual Studio to build the application.
|
||||
|
||||
|
||||
### Linux
|
||||
|
||||
ResInsight has been verified to build and run on RedHat Linux 6, but you need to install the Typical usage is to follow the build instructions above to build the makefiles. Then go to the build directory, and run:
|
||||
Typical usage is to follow the build instructions above to build the makefiles. Then go to the build directory, and run:
|
||||
|
||||
- make
|
||||
- make install
|
||||
@ -67,30 +74,48 @@ To build from the command line without using the CMake GUI:
|
||||
|
||||
You will find the ResInsight binary under the Install directory in your build directory.
|
||||
|
||||
### General CMake options for ResInsight
|
||||
### CMake Options for ResInsight
|
||||
|
||||
| CMake Name | Description |
|
||||
|--------------|---------|
|
||||
| `RESINSIGHT_BUILD_DOCUMENTATION` | Use Doxygen to create the HTML based API documentation |
|
||||
| `RESINSIGHT_PRIVATE_INSTALL` | Install as an independent bundle including the necessary Qt libraries |
|
||||
| `RESINSIGHT_USE_OPENMP` | Enable OpenMP parallellization in the code |
|
||||
| CMake Name | Default | Description |
|
||||
|---------------------------------------------------|---------|-----------------------------------------------------------------------|
|
||||
| `RESINSIGHT_BUILD_DOCUMENTATION` | OFF | Use Doxygen to create the HTML based API documentation. Doxygen must be properly installed. |
|
||||
| `RESINSIGHT_HDF5_DIR` | Blank | Windows Only: Optional path to HDF5 libraries on Windows |
|
||||
| `RESINSIGHT_INCLUDE_APPLICATION_UNIT_TESTS` | OFF | Include Application Code Unit Tests |
|
||||
| `RESINSIGHT_OCTAVE_PLUGIN_MKOCTFILE` | Blank | Optional path to the Octave tool mkoctfile used to compile Octave plugins. Needed for octave support |
|
||||
| `RESINSIGHT_OCTAVE_PLUGIN_QMAKE` | Blank | Windows Only: Set this equal to RESINSIGHT_OCTAVE_PLUGIN_MKOCTFILE |
|
||||
| `RESINSIGHT_ODB_API_DIR` | Blank | Optional path to the ABAQUS ODB API from Simulia. Needed for support of geomechanical models |
|
||||
| `RESINSIGHT_USE_OPENMP` | ON | Enable OpenMP parallellization in the code |
|
||||
|
||||
### Optional - Octave plugins
|
||||
To be able to compile the Octave plugins, the path to the Octave development tool _`mkoctfile`_ must be provided.
|
||||
#### Advanced Options
|
||||
| CMake Name | Default | Description |
|
||||
|---------------------------------------------------|---------|--------------------------------------------------------|
|
||||
| `RESINSIGHT_ENABLE_PROTOTYPE_FEATURE_FRACTURES` | ON | Enable Fracture features |
|
||||
| `RESINSIGHT_ENABLE_PROTOTYPE_FEATURE_SOURING` | ON | Enable Souring features |
|
||||
| `RESINSIGHT_PRIVATE_INSTALL` | ON | Linux only: Install the libecl shared libraries along the executable |
|
||||
| `RESINSIGHT_ENABLE_COTIRE` | OFF | Experimental speedup of compilation using cotire |
|
||||
| `RESINSIGHT_OCTAVE_PLUGIN_32_BIT` | OFF | Windows Only: Set 32-bit MSVC compiler environment while running mkoctfile |
|
||||
|
||||
It is possible to build ResInsight without compiling the Octave plugins. This can be done by specifying blank for the Octave CMake options. The Octave plugin module will not be built, and CMake will show warnings like 'Failed to find mkoctfile'. This will not break the build or compilation of ResInsight.
|
||||
### Optional Libraries and features
|
||||
|
||||
ResInsight has been verified to build and run with Octave versions 3.4.3, 3.8.1, and 4.0.0.
|
||||
#### HDF5
|
||||
|
||||
#### Octave related CMake options for ResInsight
|
||||
HDF5 is used to read SourSimRL result files. On windows this is optional, while on linux the installed HDF5 library will be used if present.
|
||||
|
||||
| CMake Name | Description |
|
||||
|--------------|---------|
|
||||
| `RESINSIGHT_OCTAVE_PLUGIN_32_BIT` | Set 32-bit MSVC compiler environment while running mkoctfile |
|
||||
| `RESINSIGHT_OCTAVE_PLUGIN_MKOCTFILE` | Location of Octave tool mkoctfile used to compile Octave plugins |
|
||||
| `RESINSIGHT_OCTAVE_PLUGIN_QMAKE` | Location of Qt version to use when compiling Octave plugins. Must be compatible with Octave runtime. (Use the Qt version embedded in Octave. The qmake executable itself is not used, only the path to the directory.) |
|
||||
Tested with 1.8.18 on windows, and default installation on RedHat 6.
|
||||
|
||||
#### Octave Dependencies for Debian Based Distributions
|
||||
#### Octave
|
||||
|
||||
To be able to compile the Octave plugins, the path to the Octave development tool _`mkoctfile`_ must be provided in the RESINSIGHT_OCTAVE_PLUGIN_MKOCTFILE. On linux this is populated automatically if Octave is installed.
|
||||
|
||||
The path to a compatible qt library must also be provided, controlled by RESINSIGHT_OCTAVE_PLUGIN_QMAKE. On linux this can be left blank.
|
||||
|
||||
It is possible to build ResInsight without compiling the Octave plugins. This can be done by specifying blank for
|
||||
the Octave CMake options. The Octave plugin module will not be built, and CMake will show warnings like 'Failed to find mkoctfile'.
|
||||
This will not break the build or compilation of ResInsight.
|
||||
|
||||
ResInsight has been verified to build and run with Octave versions 3.4.3, 3.8.1, and 4.0.0 on RedHat linux, and 4.0.0 on Windows.
|
||||
|
||||
##### Octave Dependencies for Debian Based Distributions
|
||||
|
||||
- sudo apt-get install git cmake build-essential octave octave-headers qt4-dev-tools
|
||||
|
||||
@ -98,13 +123,9 @@ If you are running Ubuntu 12.10 or newer, you will need to replace octave-header
|
||||
|
||||
- sudo apt-get install git cmake build-essential octave liboctave-dev qt4-dev-tools
|
||||
|
||||
### Optional - ABAQUS ODB API
|
||||
|
||||
ResInsight can be built with support for ABAQUS ODB files. This requires an installation of the ABAQUS ODB API from Simulia on the build computer. The path to the ABAQUS ODB API folder containing header files and library files must be specified. Leaving this option blank gives a build without ODB support. ResInsight has been built and tested with ABAQUS ODB API version 6.14-3 on Windows 7/8 and RedHat Linux 6.
|
||||
|
||||
ABAQUS ODB API related CMake options for ResInsight
|
||||
|
||||
| CMake Name | Description |
|
||||
|--------------|---------|
|
||||
| `RESINSIGHT_ODB_API_DIR` | Optional path to the ABAQUS ODB API from Simulia |
|
||||
#### ODB support
|
||||
|
||||
ResInsight can be built with support for ABAQUS ODB files. This requires an installation of the ABAQUS ODB API
|
||||
from Simulia on the build computer. The path to the ABAQUS ODB API folder containing header files and library
|
||||
files must be specified. Leaving this option blank gives a build without ODB support.
|
||||
ResInsight has been built and tested with ABAQUS ODB API version 6.14-3 on Windows 7/8/10 and RedHat Linux 6.
|
||||
|
||||
19
docs/CarfinExport.md
Normal file
19
docs/CarfinExport.md
Normal file
@ -0,0 +1,19 @@
|
||||
---
|
||||
layout: docs
|
||||
title: CARFIN Export
|
||||
permalink: /docs/carfinexport/
|
||||
published: true
|
||||
---
|
||||
|
||||
ResInsight can export a block of cells as an LGR by writing an Eclipse CARFIN keyword to a text file.
|
||||
To do this, right click an Eclipse-case in the **Project Tree** and select the command **Export CARFIN...**.
|
||||
The following dialog will open:
|
||||
|
||||
|
||||
|
||||
- **Source Case** -- The case to export from.
|
||||
- **Export Filename** -- The file to write the CARFIN keyword to.
|
||||
- **Source Grid Box** -- Options to control the box of cells defined by I, J, K and ranges to apply when exporting.
|
||||
- **Grid Refinement** -- The LGR refinement options to use within the defined gridbox.
|
||||
- **Cell Count I,J,K** -- NX, NY and NZ in the CARFIN keyword.
|
||||
- **Max Well Count** -- The NWMAX in the CARFIN keyword.
|
||||
@ -7,13 +7,13 @@ published: true
|
||||
|
||||
|
||||
|
||||
**Grid Case Group**'s are designed to make it easy to calculate statistics per cell and per timestep of a large number of Eclipse simulation Cases with identical Grids (often labeled *realizations*).
|
||||
**Grid Case Group**'s are designed to make it easy to calculate statistics per cell and per time step of a large number of Eclipse simulation Cases with identical Grids (often labeled *realizations*).
|
||||
|
||||
If you have several Eclipse simulations with different input parameters available, you can put all the realizations into a Grid Case Group and easily calculate each of the cells mean value, range and max/min values at each timestep between the realizations.
|
||||
If you have several Eclipse simulations with different input parameters available, you can put all the realizations into a Grid Case Group and easily calculate each of the cells mean value, range and max/min values at each time step between the realizations.
|
||||
|
||||
## Creating Grid Case Groups
|
||||
|
||||
### From files
|
||||
### From Files
|
||||
The easiest way to create a **Grid Case Group** is to use the Import command:
|
||||
**File->Import->Create Grid Case Group from Files**
|
||||
|
||||
@ -33,7 +33,7 @@ This is useful if you want to create statistics based only on a subset of the so
|
||||
|
||||
**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.
|
||||
|
||||
## Viewing special Source Cases
|
||||
## Viewing Special Source Cases
|
||||
To reduce the number of views, only a view for the first case is created automatically. If you want to inspect the results of a particular source case, right-click the case and select **New view** from the context menu. A new 3D View will the be created on that particular case.
|
||||
|
||||
<div class="note">
|
||||
@ -44,14 +44,14 @@ To reduce memory usage, project loading time etc. remember to delete the 3D View
|
||||
## Statistics
|
||||
After creating a grid case group, an empty **Statistics Case** is created for you in the **Derived Statistics** folder of the **Grid Case Group**.
|
||||
|
||||
### Setting up and Calculate
|
||||
### Setting Up and Calculate
|
||||
The properties of non-calculated and calculated **Statistics Case** is shown below:
|
||||
|
||||
 
|
||||
|
||||
- **Compute** -- Starts to calculate requested statistical Properties.
|
||||
- **Edit** -- Deletes the calculated results, and makes the controls to edit the setup available.
|
||||
- **Summary of calculation setup** -- Summarizes what to calculate
|
||||
- **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 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**.
|
||||
@ -68,7 +68,7 @@ The values are sorted, and the first observation representing a probability high
|
||||
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
|
||||
### 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.
|
||||
|
||||
### Adding Statistics Cases
|
||||
|
||||
@ -7,7 +7,7 @@ published: true
|
||||
|
||||
|
||||
|
||||
The main results to postprocess in ResInsight are Cell Results. A Cell Result is one value, or a small set of values per
|
||||
The main results to post process in ResInsight are Cell Results. A Cell Result is one value, or a small set of values per
|
||||
cell over a region of the grid. A Cell Result is also referred to as a *Property*.
|
||||
|
||||
Cell Results are used in several operations and settings:
|
||||
@ -19,24 +19,25 @@ Cell Results are used in several operations and settings:
|
||||
- **Well Log Extraction Curves**
|
||||
- **Cell Result Time History Curves**
|
||||
|
||||
In the property panel of all those, the same options are used to define the Cell Result of interest.
|
||||
In the property panel of all those, the same options are used to define the Cell Result of interest.
|
||||
In the following we will describe these options.
|
||||
|
||||
## Eclipse Result Types
|
||||
|
||||
As shown in the picture below, there are 6 different result types
|
||||
As shown in the picture below, there are 7 different result types
|
||||
|
||||
|
||||
|
||||
- **Dynamic** -- Time varying properties from the Eclipse simulation
|
||||
- **Static** -- Eclipse properties that does not vary with time. Some derived properties calculated by ResInsight are also present.
|
||||
- **Dynamic** -- Time varying properties from the Eclipse simulation. Some derived properties calculated by ResInsight are also present. ( See [Derived Results]({{ site.baseurl }}/docs/derivedresults) )
|
||||
- **Static** -- Eclipse properties that does not vary with time. Some derived properties calculated by ResInsight are also present.( See [Derived Results]({{ site.baseurl }}/docs/derivedresults) )
|
||||
- **SourSimRL** -- Available only if results from SourSimRL is imported. Displays the available imported results. See [SourSimRL Import]({{ site.baseurl }}/docs/gridimportexport)
|
||||
- **Generated** -- Results generated by an Octave Script ends up here
|
||||
- **Input Property** -- Directly imported Eclipse properties from ascii files is shown in this category
|
||||
- **Formation Names** -- Lists only the Active Formation Names selected on the case. ( See [Formations]({{ site.baseurl }}/docs/formations) )
|
||||
- **Flow Diagnostics** -- Flow diagnostic results are derived from the flux field in the Eclipse result data file and is only
|
||||
available if those results are present. This option is described in detail below.
|
||||
- **Flow Diagnostics** -- Flow diagnostic results are derived from a flux field. Either the fluxes stored in the Eclipse result data file or estimated fluxes. This option is described in detail below.
|
||||
- **Injection Flooding** -- Currently only the derived property **Water Flooded PV** calculated based on one or more selected simulation tracers. (See [below]({{ site.baseurl }}/docs/cellresults#injection-flooding) )
|
||||
|
||||
## Flow Diagnostic Results
|
||||
### Flow Diagnostic Results
|
||||
|
||||
ResInsight has embedded Flow Diagnostics calculations made available using the **Flow Diagnostics** result type.
|
||||
These results make it easier to see how and where wells interact with the reservoir and each other.
|
||||
@ -44,21 +45,25 @@ It is possible to select exactly what wells to investigate, and even the possibl
|
||||
|
||||
Se also [ Flow Diagnostics Plots]({{ site.baseurl }}/docs/flowdiagnosticsplots) and [ Flow Characteristics Plot]({{ site.baseurl }}/docs/flowdiagnosticsplots#flow-characteristics-plot)
|
||||
|
||||
### Method
|
||||
#### Method
|
||||
|
||||
The calculations are performed by a library called [opm-flowdiagnostics](https://github.com/OPM/opm-flowdiagnostics) developed by [SINTEF Digital](http://www.sintef.no/sintef-ikt/#/). A more elaborate description of the technique and how it can be utilized, can be found at Sintef's web site [here](http://www.sintef.no/projectweb/mrst/modules/diagnostics/). The MRST tool described is a Matlab predecessor of the flow diagnostics calculations developed for ResInsight.
|
||||
The calculations are performed by a library called [opm-flowdiagnostics](https://github.com/OPM/opm-flowdiagnostics) developed by [SINTEF Digital](http://www.sintef.no/sintef-ikt/#/).
|
||||
|
||||
This method is based on the presence of a flux field, and will use the flux field written to the eclipse result data file (Cell Properties: FLRGAS, FLRWAT, FLROIL) if available. If these are not available, the flux field is estimated by algorithms in the opm-flowdiagnostics-applications library based on pressure differences, relative and absolute permeability and viscosity. Other effects are not included.
|
||||
|
||||
A more elaborate description of the technique and how it can be utilized, can be found at Sintef's [web site](http://www.sintef.no/projectweb/mrst/modules/diagnostics/). The MRST tool described is a Matlab predecessor of the flow diagnostics calculations developed for ResInsight.
|
||||
|
||||
The methodology is also described in:
|
||||
[The application of flow diagnostics for reservoir management](http://folk.ntnu.no/andreas/papers/diagnostics.pdf) SPE J., Vol. 20, No. 2, pp. 306-323, 2015. DOI: [10.2118/171557-PA](https://dx.doi.org/10.2118/171557-PA)
|
||||
|
||||
### Cross Flow and Opposite Flow
|
||||
#### Cross Flow and Opposite Flow
|
||||
|
||||
The *opposite flow* of a well denotes the flow that is opposite to the expected normal state of the well. Eg. parts of a producer might actually be injecting due to cross flow, and an injector could be producing in some sections.
|
||||
The *opposite flow* of a well denotes the flow that is opposite to the expected normal state of the well. E.g. parts of a producer might actually be injecting due to cross flow, and an injector could be producing in some sections.
|
||||
Each well is assigned an opposite flow name by adding "-XF" to the end of the name. "-XF" was chosen as a reference to Cross Flow.
|
||||
|
||||
In this way, a producer will have two tracer names: The "well name" as a producer tracer, and "well name-XF" as an injector tracer.
|
||||
|
||||
### Defining results
|
||||
#### Defining Results
|
||||
|
||||
There are several options available to define the particular result you want to target, as shown below:
|
||||
|
||||
@ -73,6 +78,7 @@ There are two main selections you need to make: The tracers and the result prope
|
||||
- The list of selectable tracers can be filtered using wild card search of their names.
|
||||
- The tracers are sorted by their overall status as producer or injectors and prefixed depending on the status.
|
||||
Injectors are prefixed with "I :", producers with "P :" and wells with varying state "I/P:".
|
||||
- **Phases** -- Select the fluid phase you are interested in: All, Oil, Gas or Water. If one of the separate phases are selected, only the _Time Of Flight_ result property will be available in the list below.
|
||||
- **Result property** -- Displays a list of the available results:
|
||||
- **Time Of Flight (Average)** -- The time for some fluid in the cell to reach a producer,
|
||||
or the time it takes to reach the cell from an injector.
|
||||
@ -89,11 +95,19 @@ There are two main selections you need to make: The tracers and the result prope
|
||||
This produces values between 0.0 and 1.0 where high values indicate that both the injectors and the producers
|
||||
have a high influence.
|
||||
|
||||
### On-Demand Calculation
|
||||
#### On-Demand Calculation
|
||||
|
||||
The flow diagnostics results are only calculated when asked for, and only for requested timesteps. This means that statistics based on all timesteps are not available for these results.
|
||||
The flow diagnostics results are only calculated when asked for, and only for requested time steps. This means that statistics based on all time steps are not available for these results.
|
||||
|
||||
|
||||
### Injection Flooding
|
||||
|
||||
This result type is used to plot derived results based on a selection of simulated tracers, typically seawater injection. Currently the only derived property available is **Water Flooded PV**. Please refer to [Derived Results]({{ site.baseurl }}/docs/derivedresults) for more information.
|
||||
|
||||
|
||||
- **Tracers** -- Lists the available simulation tracers from the Eclipse Case. The list is produced by showing only the properties with names ending with the letter "F". Select the tracers you want to investigate.
|
||||
- **Result Property** -- Select the variable you want to calculate. (_Number Of Flooded PV_ is currently the only one)
|
||||
|
||||
## Geomechanical Results
|
||||
|
||||
Geomechanical results are sorted in different **Result Position**s:
|
||||
@ -104,6 +118,8 @@ Geomechanical results are sorted in different **Result Position**s:
|
||||
See [Element Nodal on Face]({{ site.baseurl }}/docs/derivedresults#element-nodal-on-face) for more information
|
||||
- **Formation Names** -- Lists the **Active Formation Names** selected on the case. ( See [Formations]({{ site.baseurl }}/docs/formations) )
|
||||
|
||||
Several derived cell properties are calculated. Please refer to [Derived Results]({{ site.baseurl }}/docs/derivedresults) for more information.
|
||||
|
||||
### Relative Result Options
|
||||
|
||||
This group of options controls time-lapse results to be calculated. ( See [Relative Results]({{ site.baseurl }}/docs/derivedresults#relative-results-time-lapse-results) for more information )
|
||||
|
||||
325
docs/CommandFile.md
Normal file
325
docs/CommandFile.md
Normal file
@ -0,0 +1,325 @@
|
||||
---
|
||||
layout: docs
|
||||
title: Command File
|
||||
permalink: /docs/commandfile/
|
||||
published: true
|
||||
---
|
||||
|
||||
The command file interface allows a sequence of specified commands to be run in order from the command line.
|
||||
The interface is used by supplying the command file as a [command line parameter]({{site.baseurl}}/docs/commandlineparameters).
|
||||
Once the command file is finished executing, ResInsight will exit.
|
||||
|
||||
**Case Control Commands**
|
||||
|
||||
* [openProject](#openproject)
|
||||
* [closeProject](#closeproject)
|
||||
* [setStartDir](#setstartdir)
|
||||
* [loadCase](#loadcase)
|
||||
* [replaceCase](#replacecase)
|
||||
* [replaceSourceCases](#replacesourcecases)
|
||||
|
||||
**Export Commands**
|
||||
|
||||
* [exportMultiCaseSnapshots](#exportmulticasesnapshots)
|
||||
* [exportSnapshots](#exportsnapshots)
|
||||
* [exportProperty](#exportproperty)
|
||||
* [exportWellPathCompletions](#exportwellpathcompletions)
|
||||
* [exportMsw](#exportmsw)
|
||||
* [setExportFolder](#setexportfolder)
|
||||
|
||||
**Other Commands**
|
||||
|
||||
* [runOctaveScript](#runoctavescript)
|
||||
* [setMainWindowSize](#setmainwindowsize)
|
||||
* [computeCaseGroupStatistics](#computecasegroupstatistics)
|
||||
* [setTimeStep](#settimestep)
|
||||
|
||||
|
||||
Syntax
|
||||
======
|
||||
|
||||
The command file is comprised of a set of commands to be executed in order. Each command must begin on a separate line, i.e. there cannot be two commands on the same line.
|
||||
|
||||
The line starts with the command name, followed by parenthesis. Within the parenthesis, parameters can be supplied. Each parameter must be named, followed by an equals sign and its value.
|
||||
|
||||
As an example; `openProject(path="/path/to/ResInsightProject.rsp")` will execute the command `openProject` with the parameter `path`. `path` is a string, see [Types](#types) for a list of all types a parameter can have.
|
||||
|
||||
Not all parameters are required, in which case they can be omitted and their value will be defaulted. The order of parameters does not matter.
|
||||
|
||||
Types
|
||||
-----
|
||||
|
||||
There are different types of parameters that can be supplied.
|
||||
|
||||
| Type | Input | Example |
|
||||
|---------|----------------------------------------------------------------------------------------------------|-----------------|
|
||||
| Integer | Number | 5 |
|
||||
| Double | Decimal number | 3.14 |
|
||||
| String | Sequence of characters contained in quotes (`""`)<sup>1</sup> | "/path/to/file" |
|
||||
| Enum | Choice of a set of given options | ALL |
|
||||
| Boolean | `true` or `false` | true |
|
||||
| List | Multiple choices of another type, written within square brackets (`[]`) separated by a comma (`,`) | [1, 2, 3] |
|
||||
|
||||
<sup>1</sup> The backslash (`\`) character is used as an escape character within strings, so to use a quote within a string, use `"escape \" with \""`. To input a literal backslash character, use `"\\"`.
|
||||
|
||||
Case Control Commands
|
||||
=====================
|
||||
|
||||
|
||||
openProject
|
||||
-----------
|
||||
|
||||
Opens a ResInsight project file.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|-----------|--------------------------------|--------|----------|
|
||||
| path | File path to the project file | String | ✔ |
|
||||
|
||||
### Example
|
||||
|
||||
`openProject(path="/home/user/ResInsightProject.rsp")`
|
||||
|
||||
|
||||
closeProject
|
||||
------------
|
||||
|
||||
Closes the current open project.
|
||||
|
||||
### Example
|
||||
|
||||
`closeProject()`
|
||||
|
||||
|
||||
setStartDir
|
||||
-----------
|
||||
|
||||
Set startup directory.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|-----------|------------------------------------------------|--------|----------|
|
||||
| path | Path to directory to use as startup directory | String | ✔ |
|
||||
|
||||
### Example
|
||||
|
||||
`setStartDir(path="/home/user")`
|
||||
|
||||
|
||||
loadCase
|
||||
--------
|
||||
|
||||
Import Eclipse case from file.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|-----------|--------------------------------|--------|----------|
|
||||
| path | File path to the case to load | String | ✔ |
|
||||
|
||||
### Example
|
||||
|
||||
`loadCase(path="/home/user/reservoir.EGRID")`
|
||||
|
||||
|
||||
replaceCase
|
||||
-----------
|
||||
|
||||
Replaces a case in the current project with the specified new case.
|
||||
|
||||
`openProject` must be called before this command to set which project file is to be used when replacing cases. This command re-opens the project with the new case replaced. To replace more than one case at the same time, use `replaceSourceCases`.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|-------------|----------------------------------------------------|---------|----------|
|
||||
| newGridFile | File path to the new grid file to replace with | String | ✔ |
|
||||
| caseId | ID of the case to replace. Defaults to first case | Integer | |
|
||||
|
||||
### Example
|
||||
|
||||
`replaceCase(newGridFile="/home/user/otherReservoir.EGRID", caseId=4)`
|
||||
|
||||
|
||||
replaceSourceCases
|
||||
------------------
|
||||
|
||||
Replaces multiple source cases in the current project.
|
||||
|
||||
`openProject` must be called before this command to set which project file is to be used when replacing cases. This command re-opens tje project with the cases replaced.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|--------------|-----------------------------------------------------------------|---------|----------|
|
||||
| gridListFile | File path to file containing list of cases to replace with | String | ✔ |
|
||||
| caseGroupId | ID of group to replace cases in. Defaults to first group | Integer | |
|
||||
|
||||
### Example
|
||||
|
||||
`replaceSourceCases(gridListFile="C:/resinsight/replacement_files.txt")`
|
||||
|
||||
|
||||
Export Commands
|
||||
===============
|
||||
|
||||
exportMultiCaseSnapshots
|
||||
------------------------
|
||||
|
||||
Replaces the first case in the current project with each case in the given file and saves snapshots of all views.
|
||||
|
||||
`openProject` must be called before this command to set which project file is to be used when replacing cases.
|
||||
|
||||
Folder to output snapshots should be set using `setExportFolder` with `SNAPSHOTS` type.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|--------------|--------------------------------------------------------------------|---------|----------|
|
||||
| gridListFile | File path to file containing list of cases to create snapshots of | String | ✔ |
|
||||
|
||||
### Example
|
||||
|
||||
`exportMultiCaseSnapshots(gridListFile="C:\\resinsight\\replacement_files.txt")`
|
||||
|
||||
|
||||
exportSnapshots
|
||||
---------------
|
||||
|
||||
Export snapshots of specified type.
|
||||
|
||||
Folder to output snapshots should be set using `setExportFolder` with `SNAPSHOTS` type.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|-----------|-----------------------------------------------------------------------------------|------|----------|
|
||||
| type | Type of snapshots to export. Choices: `ALL`, `VIEWS`, `PLOTS`. Defaults to `ALL` | Enum | |
|
||||
|
||||
### Example
|
||||
|
||||
`exportSnapshots(type=PLOTS)`
|
||||
|
||||
|
||||
exportProperty
|
||||
--------------
|
||||
|
||||
Exports a property to file in Eclipse format.
|
||||
|
||||
This command changes the selected property on the first view of the selected case.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|----------------|-------------------------------------------------------------------------------------------------|---------|----------|
|
||||
| caseId | ID of case to export property from | Integer | ✔ |
|
||||
| property | Name of property to export | String | ✔ |
|
||||
| eclipseKeyword | Eclipse keyword to use. Defaults to the value of `property` parameter | String | |
|
||||
| undefinedValue | Value to use for undefined values. Defaults to 0.0 | Double | |
|
||||
| exportFile | File to export to. Defaults to export folder for `PROPERTIES` with `property` name as filename | String | |
|
||||
|
||||
### Example
|
||||
|
||||
`exportProperty(caseId=1, property="SOIL")`
|
||||
|
||||
|
||||
exportWellPathCompletions
|
||||
-------------------------
|
||||
|
||||
Export well path completions.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------|
|
||||
| caseId | ID of case to export well paths for | Integer | ✔ |
|
||||
| timeStep | The time step to export completions for | Integer | ✔ |
|
||||
| wellPathNames | Names of well paths to export for. Defaults to all wells or checked wells, as determined by `wellSelection` parameter | List of String | |
|
||||
| wellSelection | Which wells are included. Choices: `ALL_WELLS`, `CHECKED_WELLS`. Defaults to `ALL_WELLS` | Enum | |
|
||||
| fileSplit | How the files are split. Choices: `UNIFIED_FILE`, `SPLIT_ON_WELL`, `SPLIT_ON_WELL_AND_COMPLETION_TYPE`. Defaults to `UNIFIED_FILE` | Enum | |
|
||||
| compdatExport | Chose whether transmissibilities are exported. Choices: `TRANSMISSIBILITIES`, `WPIMULT_AND_DEFAULT_CONNECTION_FACTORS`. Defaults to `TRANSMISSIBILITIES` | Enum | |
|
||||
| includePerforations | Whether main bore perforations should be included. Defaults to `true` | Boolean | |
|
||||
| includeFishbones | Whether fishbones should be included. Defaults to `true` | Boolean | |
|
||||
| excludeMainBoreForFishbones | Whether main bore completions shouldb be excluded for cells with fishbones. Defaults to `false` | Boolean | |
|
||||
|
||||
### Example
|
||||
|
||||
`exportWellPathCompletions(caseId=3, timeStep=5, wellSelection=CHECKED_WELLS, includeFishbones=false)`
|
||||
|
||||
|
||||
exportMsw
|
||||
---------
|
||||
|
||||
Export multi-segment wells.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|-----------|------------------------------------------------|---------|----------|
|
||||
| caseId | ID of case to export well paths for | Integer | ✔ |
|
||||
| wellPath | Name of well path to export well segments for | String | ✔ |
|
||||
|
||||
### Example
|
||||
|
||||
`exportMsw(caseId=1, wellPath="MainWell")`
|
||||
|
||||
|
||||
setExportFolder
|
||||
---------------
|
||||
|
||||
Set the folder to export different types of data to. Set this before attempting to export data to ensure it is exported to desired location.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|-----------|------------------------------------------------------------------------------------------------|--------|----------|
|
||||
| type | Type of export folder to set. Choices: `COMPLETIONS`, `SNAPSHOTS`, `PROPERTIES`, `STATISTICS` | Enum | ✔ |
|
||||
| path | Directory to export the given type to | String | ✔ |
|
||||
|
||||
### Example
|
||||
|
||||
`setExportFolder(type=SNAPSHOTS, path="/home/user/snapshots")`
|
||||
|
||||
|
||||
Other
|
||||
=====
|
||||
|
||||
runOctaveScript
|
||||
---------------
|
||||
|
||||
Execute an Octave script.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|-----------|-------------------------------------------------------------------------------------------------|-----------------|----------|
|
||||
| path | Path to the octave script to execute | Integer | ✔ |
|
||||
| caseIds | The cases to run the octave script on. Defaults to running the script without a specified case | List of Integer | |
|
||||
|
||||
### Example
|
||||
|
||||
`runOctaveScript(path="/home/user/octave/something.m", caseIds=[1,2,6])`
|
||||
|
||||
|
||||
setMainWindowSize
|
||||
-----------------
|
||||
|
||||
Resize the main window to the specified size.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|-----------|----------------------------------------|---------|----------|
|
||||
| width | The width to set for the main window | Integer | ✔ |
|
||||
| height | The height to set for the main window | Integer | ✔ |
|
||||
|
||||
### Example
|
||||
|
||||
`setMainWindowSize(width=1920, height=1200)`
|
||||
|
||||
|
||||
computeCaseGroupStatistics
|
||||
--------------------------
|
||||
|
||||
Compute statistics for statistics cases.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|-----------|----------------------------------------------------------------------|-----------------|----------|
|
||||
| caseIds | IDs of statistics cases to compute. Default is all statistics cases | List of Integer | |
|
||||
|
||||
### Example
|
||||
|
||||
`computeCaseGroupStatistics(caseIds=[5])`
|
||||
|
||||
`computeCaseGroupStatistics(caseIds=[2,4,8])`
|
||||
|
||||
|
||||
setTimeStep
|
||||
-----------
|
||||
|
||||
Set the time step for a given case. The time step is used for all views on the case.
|
||||
|
||||
| Parameter | Description | Type | Required |
|
||||
|-----------|----------------------------------|---------|----------|
|
||||
| caseId | ID of case to set time step for | Integer | ✔ |
|
||||
| timeStep | Index of time step to switch to | Integer | ✔ |
|
||||
|
||||
### Example
|
||||
|
||||
`setTimeStep(caseId=1, timeStep=8)`
|
||||
@ -18,11 +18,14 @@ Examples on how command line options are used are given in
|
||||
| --project <filename> | Open project file <filename>. |
|
||||
| --case <casename> | Import Eclipse case <casename> (do not include .GRID/.EGRID) |
|
||||
| --startdir <folder> | Set startup directory. |
|
||||
| --savesnapshots all|views|plots| | Save snapshot of all views/plots or all(both views and plots) to **snapshots** folder in project file folder. If no arugument option is given, views are exported. Application closes after snapshots have been written. |
|
||||
| --savesnapshots all|views|plots| | Save snapshot of all views/plots or all(both views and plots) to **snapshots** folder in project file folder. If no argument option is given, views are exported. Application closes after snapshots have been written. |
|
||||
| --size <width> <height> | Set size of the main application window. |
|
||||
| --replaceCase [<caseId>] <newGridFile> | Replace grid in <caseId> or first case with <newGridFile>. Repeat parameter for multiple replace operations.|
|
||||
| --replaceSourceCases [<caseGroupId>] <gridListFile> | Replace source cases in <caseGroupId> or first grid case group with the grid files listed in the <gridListFile> file. Repeat parameter for multiple replace operations.|
|
||||
| --multiCaseSnapshots <gridListFile> | For each grid file listed in the <gridListFile> file, replace the first case in the project and save snapshot of all views. |
|
||||
| --commandFile <commandFile> | Execute a command file. See [command file documentation.]({{site.baseurl}}/docs/commandfile) |
|
||||
| --commandFileProject <filename> | Project to use if performing case looping for command file. Used in conjunction with `commandFileReplaceCases`. |
|
||||
| --commandFileReplaceCases [<caseId>] <caseListFile> | Supply list of cases to replace in project, performing command file for each case. Project to replace cases in must be set with `commandFileProject`. If caseId is not supplied, first case is replaced. When supplying caseId, multiple cases may be replaced at once, by supplying several caseIds and a file containing a list of grid-files to replace with for each caseId. |
|
||||
| --help, --? | Displays help text and version info |
|
||||
| --regressiontest <folder> | Run a regression test on all sub-folders starting with `TestCase*` of the given folder. **RegressionTest.rip** files in the sub-folders will be opened and snapshots of all the views is written to the sub-sub-folder **RegTestGeneratedImages**. Then difference images is generated in the sub-sub-folder **RegTestDiffImages** based on the images in sub-sub-folder **RegTestBaseImages**. The results are presented in **ResInsightRegressionTestReport.html** that is written in the given folder. |
|
||||
| --updateregressiontestbase <folder> | For all sub-folders starting with `TestCase*`, copy the images in the sub-sub-folder **RegTestGeneratedImages** to the sub-sub-folder **RegTestBaseImages** after deleting **RegTestBaseImages** completely. |
|
||||
|
||||
401
docs/Completions.md
Normal file
401
docs/Completions.md
Normal file
@ -0,0 +1,401 @@
|
||||
---
|
||||
layout: docs
|
||||
title: Completions
|
||||
permalink: /docs/completions/
|
||||
published: true
|
||||
---
|
||||
|
||||
|
||||
Three types of completions are available for modeling and export - perforation intervals, fishbone wells and fractures. The purpose of modeling these completions, is that it enables ResInsight to export Eclipse keywords for doing more refined simulations.
|
||||
|
||||
Completions can be modeled by adding new perforation intervals, fishbones subs or fractures. Details about the completions must then be specified, such as the length of the perforation interval or number of fishbone subs and laterals. After modeling the completions, the transmissibility (cell connection factors) can be calculated and exported to the Eclipse COMPDAT Keyword.
|
||||
|
||||
For fishbones completions, multi-segment well information can even be exported to the Eclipse Keywords WELSEGS, COMPSEGS and WSEGVALV.
|
||||
|
||||
<div class="note">
|
||||
The derived cell property <b>Completion Type</b> displays wich cells are intersected by the completions.
|
||||
</div>
|
||||
( See [Derived Results, Completion Type]({{ site.baseurl }}/docs/derivedresults#completion-type) )
|
||||
|
||||
## Perforation Intervals
|
||||
|
||||
A new perforation interval on a well can be set up by right-clicking on the well in the **3D View** or in the **Project Tree**, and choosing the command **New Perforation interval**.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
After creating the perforation interval, the following properties of the perforation can be set in the property editor:
|
||||
- **Start MD**, **End MD** -- Measured depth along the well path for the perforation to start/stop.
|
||||
- **Diameter** -- Diameter of the perforation, used in calculation of transmissibility ( For details on the transmissibility calculation, see [Export of Perforation Interval Completion Data]({{ site.baseurl }}/docs/completions#export-of-perforation-interval-completion-data)).
|
||||
- **Skin Factor** -- Skin factor for the perforation, used in calculation of transmissibility.
|
||||
- **All Timesteps** -- If on, the perforation interval will be present for all time steps
|
||||
- **Start Date** -- The perforation will be included in the model for all time steps after this date. If "All TimeSteps" is turned on, this option is not available and the perforation is included for all time steps.
|
||||
|
||||
The perforation intervals will be indicated by different color along the well path.
|
||||
|
||||
|
||||
|
||||
### Import Perforation Intervals
|
||||
|
||||
Perforation intervals can be imported into ResInsight from _`*.ev`_ files. These files consist of a list of wells, and their corresponding measured depth values for perforation start and end.
|
||||
|
||||
#### Perforation Interval File Format
|
||||
|
||||
"--" is interpreted as the start of a comment. The comment ends at the end of the line.
|
||||
The files can start with a unit definition line:
|
||||
|
||||
UNITS <unitname>
|
||||
|
||||
<div class="note info">
|
||||
This line is ignored for now. The numbers are interpreted to be in the units present in the case.
|
||||
</div>
|
||||
|
||||
In the following any number of :
|
||||
|
||||
WELLNAME <well-name>
|
||||
<date> <well completion> <top mMD> <base mMD> <bore hole diameter> <skin factor>
|
||||
<date> <well completion> <top mMD> <base mMD> <bore hole diameter> <skin factor>
|
||||
|
||||
- _date_ -- Start date of the completion in the format "dd mmm yyyy". Eg `01 SEP 2006`. A special `"SOH"`date is also allowed meaning Start Of History.
|
||||
- _well completion_ -- For now, only `"perforation"` is supported
|
||||
|
||||
Here is an example:
|
||||
|
||||
UNITS METRIC
|
||||
|
||||
-- R-2 AH sidetrack into Ile/Tilje
|
||||
WELLNAME R-2AH
|
||||
"SOH" perforation 6200 6350 0.212 0 -- taget Ile 2 and Ile 3
|
||||
"SOH" perforation 7050 7133 0.212 0 -- target Tilje 3, 83 m prodint
|
||||
|
||||
-- S-2 AH
|
||||
WELLNAME S-2AH
|
||||
"SOH" perforation 4340 4369 0.212 0 -- target Garn 2, 29 m prodint (update 290915)
|
||||
01 SEP 2006 perforation 5060 6185 0.212 0 -- target Tilje 3, 1125 m prodint
|
||||
|
||||
## Fishbones
|
||||
|
||||
Fishbones are completions created by drilling or etching a set of small holes nearly perpendicular to the main bore.
|
||||
Each set of holes is created in the same operation and is callea a _sub_ while each individual hole is called a _lateral_.
|
||||
|
||||
For each well path there is a top level folder in the **Project Tree** containing all the fish bone definitions containing settings that applies to all the fishbones for this well path.
|
||||
|
||||
|
||||
|
||||
- **Fishbone Well Properties** -- Settings used when exporting well connection factors
|
||||
- **StartMD** -- the start position for the fishbones. This will be set to the highest possible value automatically, but can be set lower by the user. Gives the point along the well from which the transmissibility from the matrix to the main bore will be calculated.
|
||||
- **Main Bore Diameter** -- The hole diameter for the main bore will be used in the calculation of the transmissibility (connection factor) into the main bore.
|
||||
- **Main Bore Skin Factor** -- The skin factor for the main bore, used in calculation of the transmissibility (connection factor) into the main bore.
|
||||
For multi-segment wells there are additional parameters which should be set. These are used in the export of WELSEGS data.
|
||||
- **Multi Segment Wells** - Options used by the Well Segments Export
|
||||
- **Liner Inner eter** -- The liner inner diameter for the fishbones.
|
||||
- **Roughness Factor** -- The roughness factor used in export of main bore segments.
|
||||
- **Pressure Drop** -- can be either *Hydrostatic*, *Hydrostatic + Friction* or *Hydrostatic + Friction + Acceleration*.
|
||||
- **Length and Depth** -- Used in WELSEGS export - when specifyig the lenght and depth change for each segment
|
||||
- **Incremental** -- length / depth of given segment
|
||||
- **Absolute** -- the length down the tube or depth of the last nodal point
|
||||
|
||||
### Fishbones Subs Definition
|
||||
|
||||
To add new fishbones completions, select the **New Fishbones Subs Definition** command. This menu item is available by right clicking on **Wells** in the Porject Tree or right clicking on the well trajectory in the 3D View.
|
||||
|
||||
|
||||
|
||||
The new **Fishbones Subs Definition** (a group of fishbone subs) is created in the Project tree. Several subs definitions can be created on the same well trajectory to give more flexibility in placing of the fishbones.
|
||||
|
||||
|
||||
- **Appearance**
|
||||
- **Fishbones Color** -- The 3D View color of the fishbones created by this definition
|
||||
- **Location** -- Options to control the position and number of fishbone subs created by this definition
|
||||
- **Location Defined By** -- This setting will select how to define the location of the subs in this group.
|
||||
- **Start MD** -- Position, in Measured depth along the well, of the first fishbone Sub.
|
||||
- **End MD** -- Position of the last fishbone Sub.
|
||||
- **Number of Subs** -- Defines the number of subs to create in the defined interval
|
||||
- **Spacing** -- Spacing between the subs within the interval
|
||||
- **Measured Depths** -- The measured depth of each of the fishbone subs. If the **Location Defined By** is set to the **User Specified** this will be directly editable by the user.
|
||||
- **Laterals Configuration** -- Configures the laterals at each sub position.
|
||||
- **Laterals Per Sub** -- Number of laterals for each sub position
|
||||
- **Lenght(s)** -- Length of each lateral, in m or ft.
|
||||
- **Exit Angle** -- Exit angle for fishbone lateral, in degree.
|
||||
- **Build Angle** -- Build angle for fishbone lateral, in degree pr meter.
|
||||
- **Orientation**
|
||||
- **Fixed Angle** -- The user can specify the angle for the first lateral
|
||||
- **Random angle** -- Each sub will have a random orientation. Notice that the angle between each of the laterals will be constant, with the laterals equally spaced.
|
||||
- **Install Success Rate** -- Gives the probability of success for installation of each of the fishbones laterals. If 1, all laterals are installed.
|
||||
- **Well Properties** -- Settings to control the connection factor calculation used in [Completion Data Export]({{ site.baseurl }}/docs/completions#exporting-completion-data))
|
||||
- **Hole Diameter** -- The hole diameter of the lateral
|
||||
- **Skin Factor** -- The skin factor used in the transmissibility calculation for the lateral.
|
||||
- **Multi Segment Wells** -- Settings used for Well Segment Export
|
||||
- **Tubing Diameter** -- The diameter used in the *WELSEGS* export of the laterals.
|
||||
- **Open Hole Roughness Factor** -- Exported directly to the *WELSEGS* keyword.
|
||||
- **Tubing Roughness Factor** -- Exported directly to the *WELSEGS* keyword.
|
||||
- **ICDs per Sub** -- The number of ICD (valves) per Sub, used for calculation of total ICD area for *WSEGVALV* export.
|
||||
- **ICD Orifice Diameter** -- The Diameter of the ICD, used for calculation of ICD area for *WSEGVALV* export.
|
||||
- **ICD Flow Coefficient** -- The flow coefficient, exported directly as a part of *WSEGVALV*.
|
||||
|
||||
### Import Well Trajectories as Fishbones Laterals
|
||||
|
||||
The command **Import Completions From File** can be used to import well trajectories in the _`*.dev`_ format as fishbone laterals. The imported laterals are listed under the folder **Imported Laterals** in the **Project Tree**. These laterals behave as completions, and will be exported when exporting completion data using the settings in the property panel of the **Imported Laterals** folder.
|
||||
|
||||
|
||||
|
||||
### Export Fishbones as Well Trajectories
|
||||
|
||||
The **Export Laterals** command will export the fishbone laterals as a well trajectory into a _`*.dev*`_ -file.
|
||||
|
||||
<div class="note info">
|
||||
Notice that only the trajectory data is exported. Properties related to well segment data or Completion Data export can not be written to <code>*.dev*</code> files.
|
||||
</div>
|
||||
|
||||
## Fractures
|
||||
|
||||
Hydraulic fractures are completions created by pressurizing the reservoir at a certain point in the well, and thereby creating a crack in the formations. A substance is then injected into the crack to keep it open when relaxing the pressure.
|
||||
|
||||
Fractures in ResInsight can be added both to simulation wells and Well Trajectories, and have two main types: Eliptical fractures and StimPlan fractures.
|
||||
|
||||
### Fracture Templates
|
||||
|
||||
To create a fracture you first need a **Fracture Template**. The template collects settings that are likely to be shared among several fractures, most importantly the fracture geometry. A fracture at a particular place refers to the template, and it is thereby possible to share fracture geometry and other settings between fracture instances.
|
||||
|
||||
Fracture Templates are listed in a folder with the same name in the **Project Tree**
|
||||
|
||||
|
||||
|
||||
To create a new fracture template, right-click the **Fracture Template** item in the tree, and select either **New Ellipse Fracture Template** or **New Stimplan Fracture Template**.
|
||||
|
||||
#### Common Fracture Template Options
|
||||
|
||||
- **Geometry**
|
||||
- **Fracture Orientation** -- The fractures orientation
|
||||
- **Transverse(normal) to Well Path** -- The fracture plane is vertical and normal to the well path at the intersection point.
|
||||
- **Along Well Path** -- Fracture is vertical and along the well path. This option enables options to control the perforation length and the efficiency of the well in the fracture. See below.
|
||||
- **Azimuth** -- The fracture is vertical and in line with the Azimuth Angle (measured from North) supplied.
|
||||
- **Fracture Truncation**
|
||||
- **Fracture Containment** -- Enable this option to limit what K layers you want the fracture to influence. K-Layers outside the range will not be drained by the fracture.
|
||||
- **Top Layer** -- Topmost K-layer that the fracture will drain.
|
||||
- **Base Layer** -- Lowest K-layer that the fracture will drain.
|
||||
- **Properties** -- The availability of these options depend on the **Fracture Orientation** and the **Conductivity in Fracture** setting.
|
||||
- **Conductivity in Fracture**
|
||||
- **Finite Conductivity** -- Use a calculated conductivity for flow in the fracture. Either the StimPlan conductivity, or a constant conductivity in Ellipse fractures.
|
||||
- **Infinite Conductivity** -- Assume infinite conductivity in the fracture itself. For StimPlan fractures this will ignore the conductivity in the Stimplane data.
|
||||
- **Skin Factor** -- Used when exporting to Eclipse.
|
||||
- **Perforation Length** -- The length of the intersection between the well bore and the fracture when the fracture is along the well path ( Fractures **Along Well Path** only ).
|
||||
- **Perforation Efficiency** -- The efficiency of the wellbore-fracture perforation ( Fractures **Along Well Path** only ).
|
||||
- **Well Diameter** -- Used when exporting to Eclipse.
|
||||
|
||||
#### Ellipse Fracture Template
|
||||
|
||||
|
||||
|
||||
- **Name** -- User name of this particular fracture template
|
||||
- **Geometry**
|
||||
- **Halflength X<sub>r</sub>** -- Half the width of the ellipse
|
||||
- **Height** -- The height of the elliptical fracture
|
||||
- **Fracture Orientation** -- See above
|
||||
- **Properties** -- The availability of these options depend on the **Fracture Orientation** and the **Conductivity in Fracture** setting
|
||||
- **Permeability** -- A constant permeability inside the fracture (Used to calculate conductivity in the fracture)
|
||||
- **Width** -- Crack width (Used to calculate conductivity in the fracture)
|
||||
|
||||
#### Stimplan Fracture Template
|
||||
|
||||
Stimplan fracture templates imports XML output from the Stimplan software. These XML files contains results from a simulated hydraulic fracture, describing both geometry, varying crack width, resulting condictivity etc. as time varying quantities.
|
||||
|
||||
|
||||
|
||||
- **Name** -- User name of this particular fracture template
|
||||
- **Show StimPlan Mesh** -- Show or hide the mesh lines on the fracture in the 3D View
|
||||
- **Input**
|
||||
- **File Name** -- Path to the imported StimPLan XML-file
|
||||
- **Active Timestep Index** -- Time step in the StimPlan simulation to use for transmissibility calculations and visualization
|
||||
- **Well/fracture Intersection Depth** -- The position of the fracture along the well path as MD.
|
||||
- **Geometry**
|
||||
- **Fracture Orientation** -- See above
|
||||
- **Properties**
|
||||
- **Conductivity Scaling Factor** -- Scale the overall conductivity to do sensitivity studies.
|
||||
|
||||
### Fracture Instances
|
||||
|
||||
Instances of fractures can be created along well paths and simulation wells by right clicking the well pipe in the 3D view, or the corresponding items in the **Project Tree**.
|
||||
|
||||
|
||||
|
||||
- **Name** -- User editable name
|
||||
- **Location/Orientation**
|
||||
- **Measured depth Location** -- The measured depth
|
||||
- **Azimuth** -- Azimuth orientation of fracture.
|
||||
- **Dip** -- Dip of fracture plane
|
||||
- **Tilt** -- Rotation of fracture about its plane normal
|
||||
- **Properties**
|
||||
- **Fracture Template** -- Select the fracture template to use for this fracture.
|
||||
- **StimPlan Time Step** -- Displays the time step used by the template
|
||||
- **Perforation Length** / **Perforation Efficiency** / **Well Diameter** -- These values are copied from the new template when selecting a different one. See [Common Fracture Template Options]({{ site.baseurl }}/docs/completions#common-fracture-template-options)
|
||||
- **Fracture Center Info** -- This group displays info on where the center of the fracture is positioned. The center is defined to be where the well path intersects the fracture.
|
||||
|
||||
|
||||
## Exporting Completion Data to Eclipse
|
||||
|
||||
|
||||
|
||||
- **Export Folder** -- Folder for the exported COMPDAT file. If it does not already exist, it will be created when performing the export. The exported file will get a fixed name based on what is included in the export.
|
||||
- **Case to Apply** -- Select which case to use for the export. Matrix transmissibilities will be read from this case.
|
||||
- **Export** -- Can be *Calculated Transmissibilities* or *Default Connection Factors and WPIMULT*. If *Calculated Transmissibilities* is chosen, the transmissibilities calculated based on the case and completion data are exported directly. If the *Default Connection Factors and WPIMULT* is chosen, the information about the connections for Eclipse to be able to make the transmissibility calculaton is exported for the COMPDAT keyword. In addition, the same transmissibility calculation is performed by ResInshight, and the factor between the actual transmissibility for the connection and the Eclipse calculation is exported in the WPIMULT keyword.
|
||||
- **Well Selection** -- *All Wells* or *Checked wells* if exporting from a well path collection. *Selected wells* if exporting wells.
|
||||
- **File Split** -- *Unified File*, *Split On Well* or *Split on Well and Completion Type*. If there are completions of multiple types or along multiple wells, this parameter determines if the entries for the different wells / completion types should be in the same file or split in different files.
|
||||
- **Include Fishbones** -- Option to include or exclude fishbone completions from the export.
|
||||
- **Exclude Main Bore Transmissibility For Fishbones** -- If this options is checked on, only the transmissibilities for the fishbone laterals will be included in the export, and transmissibility along the main bore will not contribute.
|
||||
- **Include Perforations** -- Option to include or exclude perforation intervals in the export.
|
||||
- **Time step** -- Which timestep to export. This option is included since perforation intervals have a start time, and thus not all perforations need be present at all time steps.
|
||||
|
||||
### Transmissibility Calculations
|
||||
|
||||
The transmissibility calculation is performed for each direction, X, Y and Z, in an orthogonal coordinate system local to the cell.
|
||||
|
||||
Taking the X direction as an example, we first calculate the relevant permeability *K* from the Eclipse properties *PERMY* (K<sub></sub>) and PERMZ (K<sub>z</sub>):
|
||||
|
||||
|
||||
|
||||
The Peacman radius (pressure equivalent radius) for the cell is then calculated, using permeabilities and cell sizes (D<sub>y</sub> and D<sub>z</sub>):
|
||||
|
||||
|
||||
|
||||
The x-component of the transmissibility vector is calculated, using the length of the perforation in the x direction (l<sub>x</sub>), the well radius (r<sub>w</sub>) and skin factor (S):
|
||||
|
||||
|
||||
|
||||
The y and z component of the transmissibility are calculated in the same manner, and the total transmissibility is then calculated as:
|
||||
|
||||
|
||||
|
||||
If the *Export Calculated Transmissibilities* is chosen in the export setting (see [Exporting Completion Data to Eclipse](#exporting-completion-data-to-eclipse)), this value is exported in the COMPDAT keyword directly. If the *Export Default Connection Factors and WPIMULT* the transmissibility is chosen, the transmissibility is calculated as above, and in addition the transmissibility is calculated as Eclipse would do it using values other than transmissibility in the COMPDAT keyword (perforation length, well radius etc). The ratio between these transmissibilities is then exported as the WPIMULT value.
|
||||
|
||||
For an example of *COMPDAT* files exported with calculated transmissibilities and with defaults and WPIMULT values, see export of fishbones completion data below.
|
||||
|
||||
### Export of Fishbone Completion Data
|
||||
|
||||
The transmissibility calculation for the fishbones is done following the above description except that when calculating the transmissibility for the laterals, the full cell volume is split among the laterals for calculation of the transmissibility. This is done by finding the direction of the main bore, and then dividing the cell size in this direction by the number of laterals in the cell when calculating the Peaceman radius.
|
||||
|
||||
An example of the exported COMPDAT file is shown below. The calculated transmissibility contribution to the cell connection factor from each lateral or main bore part is included as a comment.
|
||||
|
||||
COMPDAT
|
||||
-- Well I J K1 K2 Status SAT TR DIAM KH S Df DIR r0
|
||||
-- Well Path B main bore : 0.0569986
|
||||
Well Path B 26 45 29 29 OPEN 1* 5.699858E-02 /
|
||||
-- Fishbone 0: Sub: 0 Lateral: 0 : 0.0021382
|
||||
-- Fishbone 0: Sub: 0 Lateral: 1 : 0.00228575
|
||||
-- Fishbone 0: Sub: 0 Lateral: 2 : 0.0126269
|
||||
-- Fishbone 0: Sub: 1 Lateral: 1 : 0.0112929
|
||||
-- Fishbone 0: Sub: 2 Lateral: 0 : 0.00566964
|
||||
-- Well Path B main bore : 0.230572
|
||||
Well Path B 27 41 15 15 OPEN 1* 2.645858E-01 /
|
||||
/
|
||||
|
||||
|
||||
For export with WPIMULT factors, the main bore diameter and direction are given in the export for cells which have both main bore and lateral contributions, while diameter and main direction of the first lateral is used for cells with no main bore contribution. Other parameters exported as part of COMPDAT are set to default.
|
||||
|
||||
The *WPIMULT* parameters are calculated, as for the perforation intervals, by ResInsight calculating both the transmissibility of the completion as described above, and in addition calculating the transmissibility based on the information exported in the COMPDAT keyword. The ratio between these two numbers is then exported as the *WPIMUT* keyword.
|
||||
|
||||
COMPDAT
|
||||
-- Well I J K1 K2 Status SAT TR DIAM KH S Df DIR r0
|
||||
-- Well Path B main bore : 0.0569986
|
||||
Well Path B 26 45 29 29 OPEN 1* 1* 0.21600 1* 0.00000 1* 'Z' /
|
||||
-- Fishbone 0: Sub: 0 Lateral: 0 : 0.0021382
|
||||
-- Fishbone 0: Sub: 0 Lateral: 1 : 0.00228575
|
||||
-- Fishbone 0: Sub: 0 Lateral: 2 : 0.0126269
|
||||
-- Fishbone 0: Sub: 1 Lateral: 1 : 0.0112929
|
||||
-- Fishbone 0: Sub: 2 Lateral: 0 : 0.00566964
|
||||
-- Well Path B main bore : 0.230572
|
||||
Well Path B 27 41 15 15 OPEN 1* 1* 0.21600 1* 0.00000 1* 'Z' /
|
||||
/
|
||||
WPIMULT
|
||||
-- Well Mult I J K
|
||||
Well Path B 0.70133 25 45 29 /
|
||||
Well Path B 25.11396 27 41 15 /
|
||||
/
|
||||
|
||||
|
||||
|
||||
## Export Well Segments
|
||||
|
||||
It is possible to export all the Fishbone Subs Definitions to a text file containing the Eclipse input data
|
||||
keywords needed to represent the fishbone part of the well as an MSW.
|
||||
|
||||
This can be done by the command **Export Well Segments** available as a context command on the **Fishbones** folder. Invoking the command will show a dialog prompting you to enter a target directory and which case to use in the calculations.
|
||||
|
||||
|
||||
|
||||
### Exported MSW Data
|
||||
|
||||
In the output file there are data for three Eclipse keyword specified.
|
||||
|
||||
##### WELSEGS
|
||||
WELSEGS defines multi-segment well. The list of entries contains information on the main stem, the ICDs at the fishbone subs and the fishbone laterals. A comment above each entry details which element (main bore / ICD / lateral) the entry is for. Example:
|
||||
|
||||
WELSEGS
|
||||
-- Name Dep 1 Tlen 1 Vol 1 Len&Dep PresDrop
|
||||
Well Path A 4137.09154 87.00000 1* ABS H-- /
|
||||
-- First Seg Last Seg Branch Num Outlet Seg Length Depth Change Diam Rough
|
||||
-- Main stem
|
||||
-- Segment for sub 0
|
||||
2 2 1 1 13.00000 0.53667 0.15200 0.00001 /
|
||||
-- Laterals
|
||||
-- Diam: MSW - Tubing Radius
|
||||
-- Rough: MSW - Open Hole Roughness Factor
|
||||
-- ICD
|
||||
3 3 2 2 0.10000 0 0.15200 0.00001 /
|
||||
-- Fishbone 0 : Sub index 0 - Lateral 0
|
||||
52 52 27 3 1.70326 -0.57276 0.00960 0.00100 /
|
||||
53 53 27 52 2.34748 -0.81635 0.00960 0.00100 /
|
||||
/
|
||||
|
||||
|
||||
- The first *WELSEGS* entry contains information about the well:
|
||||
- **Name** - Name of well
|
||||
- **Dep 1** - TVD of start MD point, as given by the user in the Fishbones **Start MD** field.
|
||||
- **Tlen 1** - Point given by the user in the Fishbones **Start MD** field.
|
||||
- **Len&Dep** - incremental or absolute, as specified by the user in the Fishbones property editor.
|
||||
- **PresDrop** - specifies what is included in the pressure drop calculation, hydrostatic, friction or acceleration. Specified by user in the Fishbones property editor.
|
||||
|
||||
- The following *WELSEGS* entries contains information about each segment:
|
||||
- **First Seg**, **Last Seg** -- Values are being exported pr segment, so both first and last segment number is the number of the segment being exported.
|
||||
- **Branch Num** -- Branch number for segment being exported.
|
||||
- **Outlet Seg** -- The segment the exported segment is connected to. For the main bore segments, this is the segment before them, for ICDs the segment number being exported and for fishbone laterals the segment on the main broe where the laterals are connected.
|
||||
- **Length** -- Length of segment (if incremental Len&Dep above) or length of segments including this along well (if absolute Len&Dep above). For ICDs length is set to 0.1.
|
||||
- **Depth Change** -- Depth of segment, incremental or abosolute as for Length. For ICDs depth is set to 0.
|
||||
- **Diam** -- Diameter of segment. For main bore and ICD entries, the liner inner diamater for the Fishbones collection is used. For laterals, an effective diameter is calculated so that the diameter exported is the diameter which, assuming a circle, would give the same area as the area between the hole diameter and the tubing diameter.
|
||||
- **Rough** -- The roughness factor as entered by the user. Notice that a different value can be specified for the main bore and the laterals, as described above.
|
||||
|
||||
|
||||
##### COMPSEGS
|
||||
An example of the COMPSEGS keyword as exported is shown below.
|
||||
|
||||
COMPSEGS
|
||||
-- Name
|
||||
Well Path A /
|
||||
-- I J K Branch no Start Length End Length Dir Pen End Range Connection Depth
|
||||
28 40 6 27 0.00000 1.70326 /
|
||||
28 40 7 27 1.70326 2.34748 /
|
||||
28 40 8 27 2.34748 2.96577 /
|
||||
/
|
||||
|
||||
The first COMPSEGS entry is a line with the well path name. Each following entry is for the segments in the well, and contaning the following field:
|
||||
- **I**, **J** and **K** -- The Eclipse cell index
|
||||
- **Branch no** -- Branch number for the segment
|
||||
- **Start Length**, **End Length** -- Start and end length along the well for the relevant segment.
|
||||
|
||||
##### WSEGVALV
|
||||
An example of the WSEGVALV keyword as exported is shown below.
|
||||
|
||||
WSEGVALV
|
||||
-- Well Name Seg No Cv Ac
|
||||
Well Path A 3 1.50000 0.00008 /
|
||||
Well Path A 5 1.50000 0.00008 /
|
||||
Well Path A 7 1.50000 0.00008 /
|
||||
/
|
||||
|
||||
The parameters exported in the WEGVALV keyword are
|
||||
- **Well Name** -- The name of the well.
|
||||
- **Seg No** -- Segment number along the well.
|
||||
- **Cv** -- The ICD Flow Coefficient, as entered by the user.
|
||||
- **Ac** -- the total ICD area per sub, calculated as the area per ICD (given by the orifice radius) multiplied with the number of icd per Sub.
|
||||
|
||||
96
docs/CurveCalculator.md
Normal file
96
docs/CurveCalculator.md
Normal file
@ -0,0 +1,96 @@
|
||||
---
|
||||
layout: docs
|
||||
title: Curve Calculator
|
||||
permalink: /docs/curvecalculator/
|
||||
published: true
|
||||
---
|
||||
|
||||
|
||||
|
||||
The summary curve calculator is a tool to do relative simple vector calculations on a set of curves. The created curves can be stored for later use in the project.
|
||||
|
||||
The calculator can be run by pressing the calculator icon  in the menu bar, or by right-clicking on either a summary case or the summary plot collection.
|
||||
|
||||
## Calculation Settings
|
||||
To make a new calculated curve, click on **New Calculation**. This will add a new calculation to **Calculated Summaries**. Before choosing which curves to do calculations on, a calculation expression must be made. The default expression *Calculation_1 := x + y* will do a vector addition on the curves which *x* and *y* are placeholders for, and assign it to the calculation *Calculation_1*. How to assign curves to assign to *x* and *y* will be covered in section [Summary Address Selection](#summary-address-selection).
|
||||
|
||||
### Operators and Functions
|
||||
Possible operations and functions are found by right-clicking in the expression window. The following tables show all the options available.
|
||||
|
||||
#### Assignment Operators
|
||||
|
||||
| OPERATOR | DEFINITION |
|
||||
|----------|-----------------------|
|
||||
| := | Assign |
|
||||
|
||||
#### Basic Operators
|
||||
|
||||
| OPERATOR | DEFINITION |
|
||||
|----------|-----------------|
|
||||
| + | Addition |
|
||||
| - | Subtraction |
|
||||
| * | Multiplication |
|
||||
| / | Division |
|
||||
| % | Modulus |
|
||||
| ^ | Power |
|
||||
|
||||
#### Scalar Functions
|
||||
|
||||
| FUNCTION | DEFINITION |
|
||||
|----------|-------------|
|
||||
| avg | Average |
|
||||
| max | Maximum |
|
||||
| min | Minimum |
|
||||
| sum | Sum |
|
||||
|
||||
#### Trigonometry Functions
|
||||
|
||||
| FUNCTION | DEFINITION |
|
||||
|----------|-----------------------------------------|
|
||||
| acos | Arc cosine (in radians) |
|
||||
| acosh | Inverse hyperbolic cosine (in radians) |
|
||||
| asin | Arc sine (in radians) |
|
||||
| asinh | Inverse hyperbolic sine (in radians) |
|
||||
| atan | Arc tangent (in radians) |
|
||||
| atanh | Inverse hyperbolic tangent (in radians) |
|
||||
| cos | Cosine |
|
||||
| cosh | Hyperbolic cosine |
|
||||
| cot | Cotangent |
|
||||
| csc | Cosecant |
|
||||
| deg2rad | Convert x from degrees to radians |
|
||||
| deg2grad | Convert x from degrees to radians |
|
||||
| rad2deg | Convert x from radians to degrees |
|
||||
| grad2deg | Convert x from radians to degrees |
|
||||
| sec | Secant |
|
||||
| sin | Sine |
|
||||
| sinc | Sine cardinal |
|
||||
| sinh | Hyperbolic sine |
|
||||
| tan | Tangent |
|
||||
| tanh | Hyperbolic tangent |
|
||||
|
||||
#### Vector Functions
|
||||
|
||||
| FUNCTION | DEFINITION |
|
||||
|----------|---------------------------------------------------------|
|
||||
| abs | Absolute value |
|
||||
| ceil | Rounding up |
|
||||
| floor | Rounding down |
|
||||
| frac | Fractional portion of input |
|
||||
| log | Natural logarithm |
|
||||
| log10 | Base 10 logarithm |
|
||||
| pow | Power |
|
||||
| round | Round x to the nearest integer |
|
||||
| sgn | Sign of x, -1 where x < 0, +1 where x > 0, else zero |
|
||||
| sqrt | Square root |
|
||||
| trunc | Integer portion of input |
|
||||
|
||||
### Unit
|
||||
It is possible to add a unit to the calculated curve, in the field **Unit** beneath the expression field. This will be used as the label on the y-axis when the curve is used in a plot.
|
||||
|
||||
## Summary Address Selection
|
||||
An expression consists of placeholders (variables) for curves (summary address). By clicking **Parse Expression**, the variables will appear in the table below the settings. To assign a summary address to a variable, click **Edit**. This action will open a **Summary Address Selection** dialog. Use the dialog to select a summary address and press **OK**. Repeat the procedure for all the variables.
|
||||
|
||||
## Generating Curves
|
||||
After assigning summary addresses to all variables, click **Calculate** to evaluate the expression. The curve is saved and can be accessed in the Plot Editor selecting the Summary Type: **Calculated**.
|
||||
|
||||
The curves can also be found in an existing curve's **Property Editor**. Choose the case **Calculated**, and the curves will appear in **Vector Selection**.
|
||||
@ -7,39 +7,62 @@ published: true
|
||||
|
||||
ResInsight computes several derived results. In this section we will explain what they are, and briefly how they are calculated.
|
||||
|
||||
## Derived results for Eclipse cases
|
||||
## Derived Results for Eclipse Cases
|
||||
|
||||
The derived results are listed at the bottom of the **Static** result properties, as shown below.
|
||||
ResInsight calculates several derived cell properties that is made available as **Static** or **Dynamic** cell properties.
|
||||
The derived results listed at the bottom of the **Static** result properties, are shown below.
|
||||
|
||||
|
||||
|
||||
|
||||
### Transmissibility normalized by area
|
||||
The transmissibility for cells and Non-Neighbor Connections (NNCs) are dependent on both cell properties and geometry. ResInsight normalizes TRANX, TRANY and TRANZ with the overlapping flow area for both neighbor cells and NNC-cells. The results are named riTRANXbyArea, riTRANYbyArea and riTRANZbyArea respectively.
|
||||
### Transmissibility Normalized by Area
|
||||
The transmissibility for cells and Non-Neighbor Connections (NNCs) are dependent on both cell properties and geometry. ResInsight normalizes TRANX, TRANY and TRANZ with the overlapping flow area for both neighbor cells and NNC-cells. The results are named **riTRANXbyArea**, **riTRANYbyArea** and **riTRANZbyArea** respectively.
|
||||
|
||||
The normalized transmissibilities make it easier to compare and check the flow capacity visually. This can be useful when history matching pressure differences across a fault.
|
||||
|
||||
### Identification of questionable NNCs
|
||||
|
||||
### Overall Transmissibility Multiplier
|
||||
Transmissibility can be set or adjusted with multiple keywords in an Eclipse data deck. To visualize the adjustments made, ResInsight calculates a multiplicator for the overall change. First unadjusted transmissibilities for all neighbor cells and NNCs are evaluated based on geometry and permeabilities, similar to the NEWTRAN algorithm in Eclipse. For x- and y-directions, the NTG parameter is also included. The results are named **riTRANX**, **riTRANY** and **riTRANZ** respectively.
|
||||
|
||||
The TRANX, TRANY and TRANZ used in the simulation are divided by the ResInsight calculated transmissibilities and the resulting multiplicators are named **riMULTX**, **riMULTY** and **riMULTZ** respectively. The derived properties are listed under **Static** properties. The riMULT-properties are useful for quality checking consistence in user input for fault seal along a fault plane.
|
||||
|
||||
### Directional Combined Results
|
||||
|
||||
Cell properties with names ending in I, J, K, X, Y, or Z, and an optional "+" or "-" are combined into derived results postfixed with IJK, or XYZ depending on their origin. (Eg. the static cell properties MULTX, MULTY, MULTZ, and their negatives are combined into the result MULTXYZ, while the dynamic cell properties FLRGASI, FLRGASJ, FLRGASK are combined to FLRGASIJK).
|
||||
|
||||
These combined cell properties visualize the property as a color in all directions combined when selected in
|
||||
as a **Cell Result** and **Separate Fault Result**.
|
||||
|
||||
The face of a cell is then colored based on the value associated with that particular face. The Positive I-face of the cell gets the cell X/I-value, while the J-face gets the Y/J-value etc. The negative faces, however, get the value from the neighbor cell on that side. The negative I-face gets the X-value of the IJK-neighbor in negative I direction, and so on for the J- and K-faces.
|
||||
|
||||
The directional combined parameters available are:
|
||||
|
||||
- Static Properties
|
||||
- **TRANXYZ** (inluding NNCs)
|
||||
- **MULTXYZ**
|
||||
- **riTRANXYZ** (inluding NNCs)
|
||||
- **riMULTXYZ** (inluding NNCs)
|
||||
- **riTRANXYZbyArea** (inluding NNCs)
|
||||
- Dynamic Properties
|
||||
- **FLRWATIJK** (inluding NNCs)
|
||||
- **FLROILIJK** (inluding NNCs)
|
||||
- **FLRGASIJK** (inluding NNCs)
|
||||
- Generated
|
||||
- Octave generated results with same name but ending with I,J and K will also be combined into a _`<name>IJK`_ cell property.
|
||||
|
||||
### Completion Type
|
||||
|
||||
|
||||
|
||||
The dynamic cell property named **Completion Type** is calculated from the intersections between [Completions]({{ site.baseurl }}/docs/completions) and the grid cells. All grid cells intersected by a completion will be assigned a color based on the type of completion that intersects the cell.
|
||||
|
||||
### Identification of Questionable NNCs
|
||||
In the process of normalizing transmissibility by the overlapping flow area, the NNCs in the model without any shared surface between two cells are identified. These NNCs are listed in the **Faults/NNCs With No Common Area** folder. These NNCs are questionable since flow normally is associated with a flow area.
|
||||
|
||||
|
||||
|
||||
### Water Flooded PV
|
||||
|
||||
### Overall transmissibility multiplyer
|
||||
Transmissibility can be set or adjusted with multiple keywords in an Eclipse data deck. To visualize the adjustments made, ResInsight calculates a multiplicator for the overall change. First unadjusted transmissibilities for all neighbor cells and NNCs are evaluated based on geometry and permeabilities, similar to the NEWTRAN algorithm in Eclipse. For x- and y-directions, the NTG parameter is also included. The results are named riTRANX, riTRANY and riTRANZ respectively.
|
||||
|
||||
The TRANX, TRANY and TRANZ used in the simulation are divided by the ResInsight calculated transmissibilities and the resulting multiplicators are named riMULTX, riMULTY and riMULTZ respectively. The derived properties are listed under **Static** properties. The riMULT-properties are useful for quality checking consistence in user input for fault seal along a fault plane.
|
||||
|
||||
### Directional combined results
|
||||
Some static properties with directional dependency can be visualized in x-, y- and z-direction combined in **Cell Result** and **Separate Fault Result**. The face of a cell is then colored based on the value associated with that particular face. The Positive I-face of the cell gets the cell X-value, while the J-face gets the Y-value etc. The negative faces, however, get the value from the neighbor cell on that side. The negative I-face gets the X-value of the IJK-neighbor in negative I direction, and so on for the J- and K-faces.
|
||||
|
||||
The directional combined parameters available are:
|
||||
|
||||
- **TRANXYZ** (inluding NNCs)
|
||||
- **MULTXYZ**
|
||||
- **riTRANXYZ** (inluding NNCs)
|
||||
- **riMULTXYZ** (inluding NNCs)
|
||||
- **riTRANXYZbyArea** (inluding NNCs)
|
||||
Water Flooded PV, also called _Number of flooded porevolumes_ shows the amount of flow from a selected set of simulation tracers into a particular cell, compared to the cells mobile pore volume. A value of 1.0 will tell that the tracers accumulated flow into the cell has reached a volume equal to the mobile pore volume in the cell.
|
||||
|
||||
## Derived Geomechanical results
|
||||
|
||||
@ -97,7 +120,7 @@ The calculated result fields are:
|
||||
* FAULTMOB
|
||||
* PCRIT
|
||||
|
||||
#### Definitions of derived results
|
||||
#### Definitions of Derived Results
|
||||
|
||||
In this text the label Sa and Ea will be used to denote the unchanged stress and strain tensor respectively from the odb file.
|
||||
|
||||
@ -108,7 +131,7 @@ Components with two subscripts however, refers to the global directions 1, 2, an
|
||||
- Inclination is measured from the downwards direction
|
||||
- Azimuth is measured from the Northing (Y) Axis in Clockwise direction looking down.
|
||||
|
||||
##### Case constants
|
||||
##### Case Constants
|
||||
|
||||
Two constants can be assigned to a Geomechanical case:
|
||||
|
||||
@ -119,7 +142,7 @@ In the following they are denoted s0 and fa respectively. Some of the derived re
|
||||
|
||||
|
||||
|
||||
##### ST - Total stress
|
||||
##### ST - Total Stress
|
||||
|
||||
ST<sub>ii</sub> = -Sa<sub>ii</sub> + POR (i= 1,2,3)
|
||||
|
||||
@ -137,7 +160,7 @@ STM = (ST<sub>11</sub> + ST<sub>22</sub> + ST<sub>33</sub>)/3
|
||||
|
||||
Q = sqrt( (3/2) * ( (ST<sub>1</sub> – STM)<sup>2</sup> + (ST<sub>2</sub> – STM)<sup>2</sup> + (ST<sub>3</sub> – STM)<sup>2</sup> ))
|
||||
|
||||
##### Gamma - Stress path
|
||||
##### Gamma - Stress Path
|
||||
|
||||
Gamma<sub>ii</sub> = ST<sub>ii</sub>/POR (i= 1,2,3)
|
||||
|
||||
@ -198,7 +221,7 @@ a coordinate system is established such that:
|
||||
|
||||
The stress tensors in that particular face are then transformed to that coordinate system. The following quantities are derived from the transformed tensor named TS in the following:
|
||||
|
||||
##### SN - Stress component normal to face
|
||||
##### SN - Stress component Normal to face
|
||||
|
||||
SN = TS<sub>33</sub>
|
||||
|
||||
@ -220,7 +243,7 @@ Angle of the total in-plane shear relative to the Quasi Vertical direction
|
||||
|
||||
TPinc = acos(TPQV/TP)
|
||||
|
||||
##### Pinc and Pazi - Face inclination and Azimuth
|
||||
##### Pinc and Pazi - Face Inclination and Azimuth
|
||||
|
||||
These are the directional angles of the face-normal itself.
|
||||
|
||||
|
||||
@ -23,7 +23,7 @@ The following dialog will appear:
|
||||
- **Eclipse Keyword** -- The keyword to use for the property in the eclipse file
|
||||
- **Undefined Value** -- This value is written to the file for all values that are flagged as undefined in ResInsight
|
||||
|
||||
### File format
|
||||
### File Format
|
||||
|
||||
The exported file has the following format, that matches the Eclipse input format:
|
||||
|
||||
|
||||
22
docs/ExportFluxnumMultnum.md
Normal file
22
docs/ExportFluxnumMultnum.md
Normal file
@ -0,0 +1,22 @@
|
||||
---
|
||||
layout: docs
|
||||
title: FLUXNUM/MULTNUM
|
||||
permalink: /docs/exportfluxnummultnum/
|
||||
published: true
|
||||
---
|
||||
The visible cells can be exported as a FLUXNUM or MULTNUM keyword that can be used in an Eclipse input data deck.
|
||||
|
||||
You can do this by using the command **Export Visible Cells as FLUXNUM/MULTNUM** found by right clicking:
|
||||
- **View** in the Project Tree.
|
||||
- **Cell Result** in the Project Tree.
|
||||
- In any Eclipse **3D View**.
|
||||
|
||||
The command can also be found in **File -> Export**. If the command is used in the project tree, the visible cells from the selected view are used for calculation. In the 3D view and from File -> Export, the visible cells from the currently active 3D view are used.
|
||||
|
||||
|
||||
|
||||
- **Export Filename** -- Name of the file to export to.
|
||||
- **Export Keyword** -- Selects the Eclipse keyword to export.
|
||||
- **Visible Active Cells Value** -- This value is used for all the active cells that passes the filters(Range Filter, Property Filter etc) in the 3D View, and thus is visible.
|
||||
- **Hidden Active Cells Value** -- All the active cells that are not visible in the 3D view.
|
||||
- **Inactive Cells Value** -- This value is used for all inactive cells, regardless of whether they are visible or not.
|
||||
@ -35,28 +35,28 @@ As import of faults can be time consuming, reading of faults can be disabled fro
|
||||
If enabled in **Preferences**, ResInsight will read Non Neighbor Connections from the Eclipse output file (_`*.INIT`_), and create explicit visualizations of those.
|
||||
The NNC's are sorted onto the Fault's and their visibility is controlled along with them.
|
||||
|
||||
## Fault visualization options
|
||||
## Fault Visualization Options
|
||||
|
||||
### Fault visibility
|
||||
### Fault Visibility
|
||||
Faults can be hidden and shown in several ways.
|
||||
|
||||
- Checking or unchecking the checkbox in front of the fault will show or hide the fault.
|
||||
- Visibility for multiple faults can be controlled at the same time by selecting multiple faults and use the context menu: **On**, **Off** and **Toggle**.
|
||||
- Right-clicking a Fault in the 3D View will enable a context menu with a command to hide the fault.
|
||||
|
||||
### Fault color
|
||||
### Fault Color
|
||||
Each named Fault is given a color on import. This color can be controlled by selecting the fault and edit its **Fault color** in the **Property Editor.**
|
||||
|
||||
### Separate Fault Result
|
||||
The default result mapping used on faults are to use the same as specified in **Cell Result**. If a different result mapping is wanted, enable the checkbox at **Separate Fault Result** and select the result from the result selection dialog in the **Property Editor**. A second legend for the fault result is then added to the view.
|
||||
|
||||
### Toolbar control
|
||||
### Toolbar Control
|
||||
Visualization mode and mesh lines can be controlled from the toolbar.
|
||||
|
||||
-  **Faults-Only** visualization mode.
|
||||
<br>When turned on, this option hides all the grid cells, and shows only the fault faces in the reservoir limited by the applied range and property filters. (Unless **Show faults outside filters** are turned on. See below.)
|
||||
-  Turns faces on and mesh off
|
||||
-  Turns on all faces, and shows meshlines on faults only.
|
||||
-  Turns on all faces, and shows mesh lines on faults only.
|
||||
<br> This is a useful method to highlight the faults in your reservoir, because the faults stands out with black outlining.
|
||||
-  Shows labels for faults
|
||||
|
||||
@ -65,19 +65,19 @@ By clicking the  **Fau
|
||||
|
||||
|
||||
|
||||
##### Fault labels
|
||||
##### Fault Labels
|
||||
- **Show labels** -- Displays one label per fault with the name defined in the _`*.DATA`_ file
|
||||
- **Label color** -- Defines the label color
|
||||
|
||||
##### Fault options
|
||||
##### Fault Options
|
||||
- **Show faults outside filters** -- Turning this option on, will display faults outside the filter region, making the fault visualization completely ignore the Range and Property filters in action.
|
||||
|
||||
##### Fault Face Visibility
|
||||
This group of options controls the visibility of the fault faces. Since they work together, and in some cases are overridden by the system, they can be a bit confusing.
|
||||
|
||||
First of all. These options are only available in **Faults-only** visualization mode. ( See *Toolbar Control* above) When not in **Faults-Only** mode, ResInsight overrides the options, and the controls are inactive.
|
||||
First of all, these options are only available in **Faults-only** visualization mode ( See [Toolbar Control](#toolbar-control) ). When not in **Faults-Only** mode, ResInsight overrides the options, and the controls are inactive.
|
||||
|
||||
Secondly: The option you would normally want to adjust is **Dynamic Face Selection** ( See below ).
|
||||
Secondly, the option you would normally want to adjust is **Dynamic Face Selection** ( See below ).
|
||||
|
||||
- **Show defined faces** -- Displays the fault cell faces that are defined on the Eclipse input file (_`*.DATA`_)
|
||||
- **Show opposite faces** -- Displays the opposite fault cell faces from what is defined on the input file, based on IJK neighbors.
|
||||
|
||||
@ -8,15 +8,15 @@ published: true
|
||||
|
||||
Cell Filters are used to control visibility of the cells in the 3D view. Two types of filters exists:
|
||||
|
||||
- **Range filter** -- Extracts an IJK subset of the model.
|
||||
- **Property filter** -- Extracts cells with a property value matching a value range.
|
||||
- **Range Filter** -- Extracts an IJK subset of the model.
|
||||
- **Property Filter** -- Extracts cells with a property value matching a value range.
|
||||
|
||||
<div class="note">
|
||||
The visibilities of cells connection to wells, and fences based on these cells can be controlled from <b> <a href="{{ site.baseurl }}/docs/simulationwells">Simulation Wells</a> </b>.<br>
|
||||
<small><i>(Not applicable for Geomechanical cases)</i></small>
|
||||
</div>
|
||||
|
||||
## Common properties for Range and Property Filters
|
||||
## Common Properties for Range and Property Filters
|
||||
|
||||
Both filter types can be turned on or off using the toggle in the **Project Tree** and controlled from their corresponding **Property Editor**.
|
||||
|
||||
@ -37,7 +37,7 @@ Each *Include* range filter will *add more cells* to the visualization. The view
|
||||
A new range filter can be added by activating the context menu for the **Range Filters** collection in the **Project Tree**.
|
||||
|
||||
<div class="note">
|
||||
An I,J or K-slice range filter can be added directly from a Cell in the <b>3D View</b> by rightclicking the cell and using the context menu.
|
||||
An I,J or K-slice range filter can be added directly from a Cell in the <b>3D View</b> by right-clicking the cell and using the context menu.
|
||||
</div>
|
||||
|
||||
Below is a snapshot of the **Property Editor** of the **Range Filter** :
|
||||
@ -52,9 +52,9 @@ The **Start** and **Width** labels in front of the sliders features a number in
|
||||
The **Start** labels shows the index of the start of the active cells.<br>
|
||||
The **Width** labels shows the number of active cells from the start of the active cells.
|
||||
|
||||
## Property filters
|
||||
## Property Filters
|
||||
|
||||
**Property filters** applies to the results of the **Range filters** and limits the visible cells to the ones approved by the filter. For a cell to be visible it must be accepted by all the property filters.
|
||||
**Property Filters** applies to the results of the **Range Filters** and limits the visible cells to the ones approved by the filter. For a cell to be visible it must be accepted by all the property filters.
|
||||
|
||||
A new property filter can be made by activating the context menu on **Property Filters** or by right-clicking inside a 3D view. The new property filter is based on the currently viewed cell result by default.
|
||||
|
||||
@ -68,15 +68,15 @@ Below is a snapshot of the **Property Editor** of the **Property Filter**.
|
||||
|
||||
|
||||
|
||||
### Property value range
|
||||
### Property Value Range
|
||||
The filter is based on a property value range (Min - Max). Cells in the range are either shown or hidden depending on the **Filter Type** (*Include*/*Exclude*). Exclude-filters removes the selected cells from the **View** even if some other filter includes them.
|
||||
|
||||
#### Range Behavior for Flow Diagnostic results
|
||||
Normally the available range in the sliders is the max and min of all the values in all the timesteps. For Flow Diagnostics results, however, the available range is based on the current timestep.
|
||||
#### Range Behavior for Flow Diagnostic Results
|
||||
Normally the available range in the sliders is the max and min of all the values in all the time steps. For Flow Diagnostics results, however, the available range is based on the current time step.
|
||||
|
||||
We still need to keep the range somewhat fixed while moving from timestep to timestep, so in order to do so ResInsight tries to keep the intentions of your range settings, as the available range changes. If either the max or min value is set to the limit, ResInsight will keep that setting at the limit even when the limit changes. If you set a spesific value for the max or the min, that setting will keep its value, even if it happens to end up outside the available range at a time step.
|
||||
We still need to keep the range somewhat fixed while moving from time step to time step, so in order to do so ResInsight tries to keep the intentions of your range settings, as the available range changes. If either the max or min value is set to the limit, ResInsight will keep that setting at the limit even when the limit changes. If you set a specific value for the max or the min, that setting will keep its value, even if it happens to end up outside the available range at a time step.
|
||||
|
||||
### Category selection
|
||||
### Category Selection
|
||||
If the property is representing integer values, well tracer names or [ formation names ]({{ site.baseurl }}/docs/formations), the property filter displays a list of available categories used to filter cells. The separate values can then be toggled on or off using the list in the Property Editor.
|
||||
|
||||
|
||||
|
||||
@ -6,20 +6,26 @@ published: true
|
||||
---
|
||||
|
||||
|
||||
Flow Diagnostics Plots are managed from the **Project Tree** of the **Plot Main Window** in the folder **Flow Diagnostics Plots**. This folder contains a **Flow Characteristics Plot**, a default **Well Allocation Plot** and a **Stored Plots** folder containing stored **Well Allocation Plots**.
|
||||
Flow Diagnostics Plots can be used to view well allocation, well inflow rates, cumulative saturation along time of flight and flow characteristics.
|
||||
|
||||
They are managed from the folder **Flow Diagnostics Plots** located in **Plot Project Tree** in the **Plot Main Window**.
|
||||
|
||||
|
||||
|
||||
Please refer to [Cell Results-> Flow Diagnostic Results]({{ site.baseurl }}/docs/cellresults#flow-diagnostic-results) for more description of the results and references to more information about the methodology.
|
||||
This folder contains a default **Flow Characteristics Plot** and **Well Allocation Plot**. In addition, two folders with stored well allocation and flow characteristics plots will show up if there are any of those in the model.
|
||||
|
||||
Please refer to [Cell Results-> Flow Diagnostic Results]({{ site.baseurl }}/docs/cellresults#flow-diagnostic-results) for a description of the results and references to more information about the methodology.
|
||||
|
||||
## Well Allocation Plots
|
||||
|
||||
Well allocation plots show the flow along a specified well, along with either phase distribution or the amount of support from/to other wells. The total phase or allocation is shown in the legend and as a pie chart, while the well flow is shown in a depth value vs flow graph.
|
||||
|
||||
In addition a **Cumulative Saturation by Time of Flight** plot may be shown. This little plot illustrates how the total saturation changes as you go from the well-connection-cells along increasing time of flight adding the cells as you go.
|
||||
|
||||
### Branches
|
||||
|
||||
Each branch of the well will be assigned a separate **Track**. For normal wells this is based on the branch detection algorithm used for Well Pipe visualization, and will correspond to the pipe visualization with **Branch Detection** *On*. ( See [Well Pipe Geometry]({{ site.baseurl }}/docs/simulationwells#well-pipe-geometry) )
|
||||
Multi Segment Wells will be displayed according to their branch information, but tiny branches consisting of only one connection are lumped into the main branch to make the visualization more understandable. ( See [Dummy branches]({{ site.baseurl }}/docs/simulationwells#dummy-branches) )
|
||||
Each branch of the well will be assigned a separate **Track**. For normal wells this is based on the branch detection algorithm used for Well Pipe visualization, and will correspond to the pipe visualization with **Branch Detection** *On* ( See [Well Pipe Geometry]({{ site.baseurl }}/docs/simulationwells#well-pipe-geometry) ).
|
||||
Multi Segment Wells will be displayed according to their branch information, but tiny branches consisting of only one connection are lumped into the main branch to make the visualization more understandable ( See [Dummy branches]({{ site.baseurl }}/docs/simulationwells#dummy-branches) ).
|
||||
|
||||
### Creating Well Allocation Plots
|
||||
|
||||
@ -31,7 +37,7 @@ The command updates the default **Well Allocation Plot** with new values based o
|
||||
|
||||
### Options
|
||||
|
||||
The **Legend**, **Total Allocation** pie chart, and the **Well Flow/Allocation** can be turned on or off from the toggles in the **Project Tree**. The other options are controlled from the property panel of a Well Allocation Plot:
|
||||
The **Legend**, **Total Allocation** pie chart, **Cumulative Saturation**, and the **Well Flow/Allocation** can be turned on or off from the toggles in the **Project Tree**. The other options are controlled from the property panel of a Well Allocation Plot:
|
||||
|
||||
|
||||
|
||||
@ -44,14 +50,13 @@ The **Legend**, **Total Allocation** pie chart, and the **Well Flow/Allocation**
|
||||
- **Options**
|
||||
- **Plot Type**
|
||||
- **Allocation** -- Plots *Reservoir well flow rates* along with how this well supports/are
|
||||
supported by other wells.
|
||||
( This option is only available for cases with Flux results available. )
|
||||
- **Well Flow** -- Plots *Surface Well Flow Rates* together with phase split between Oil, Gas, and Water.
|
||||
supported by other wells ( This option is only available for cases with Flux results available )
|
||||
- **Well Flow** -- Plots *Surface Well Flow Rates* together with phase split between Oil, Gas, and Water
|
||||
- **Flow Type**
|
||||
- **Accumulated** -- Plots an approximation of the accumulated flow along the well
|
||||
- **Inflow Rates** -- Plots the rate of flow from the connection into the well
|
||||
- **Group Small Contributions** -- Groups small well contributions into a group called **Other**
|
||||
- **Threshold** -- Threshold used by the **Group Small Contributions** option.
|
||||
- **Threshold** -- Threshold used by the **Group Small Contributions** option
|
||||
|
||||
### Depth Settings
|
||||
|
||||
@ -59,18 +64,17 @@ The depth value in the plot can be controlled by selecting the **Accumulated Flo
|
||||
|
||||
|
||||
|
||||
- **Name** -- The plot name, updated automatically based on the **Flow Type** and well
|
||||
- **Name** -- The plot name, updated automatically based on the **Flow Type** and well.
|
||||
- **Depth Type**
|
||||
- **Pseudo Length** -- Use the length along the visualized simulation well pipe as depth.
|
||||
In this mode the curves are extended somewhat above zero depth keeping the curve
|
||||
values constant. This is done to make it easier to see the final values of the curves relative to each other.
|
||||
The depth are calculated with **Branch detection** *On* and using the **Interpolated** well pipe geometry.
|
||||
( See [Well Pipe Geometry]({{ site.baseurl }}/docs/simulationwells#well-pipe-geometry) )
|
||||
- **TVD** -- Use True Vertical Depth on the depth-axis.
|
||||
This will produce distorted plots for horizontal or near horizontal wells.
|
||||
- **TVD** -- Use True Vertical Depth on the depth-axis. This will produce distorted plots for horizontal or near horizontal wells.
|
||||
- **Connection Number** -- Use the number of connections counted from the top on the depth-axis.
|
||||
- **Visible Depth Range** -- These options control the depth zoom
|
||||
- **Auto Scale** -- Toggles autoscale on/off. The plot is autoscaled when significant changes to its settings are made
|
||||
- **Visible Depth Range** -- These options control the depth zoom.
|
||||
- **Auto Scale** -- Toggles autoscale on/off. The plot is autoscaled when significant changes to its settings are made.
|
||||
- **Min**, **Max** -- Sets the visible depth range. These are updated when zooming using the mouse wheel etc.
|
||||
|
||||
### Accessing the Plot Data
|
||||
@ -83,12 +87,36 @@ The total accumulation data can also be viewed in ascci format by the command **
|
||||
|
||||
## Flow Characteristics Plot
|
||||
|
||||
This window displays three different graphs describing the overall behaviour of the reservoir for each timestep from a flow diagnostics point of view.
|
||||
|
||||
The timesteps available are only those already calculated by the flow diagnostics solver. That means timesteps for which flow diagnostic results have been requested either by Cell Results, Well Allocation Plots, or Well Log Extraction Curves.
|
||||
|
||||
|
||||
|
||||
- **Lorenz Coefficient** -- This plot displays the Lorenz coefficient for the complete reservoir for each calculated timestep. The time step color is used as a reference for the timestep in the other graphs.
|
||||
- **Flow Capacity vs Storage Capacity** -- This plot displays one curve for each timestep of the F-phi curve for the reservoir.
|
||||
- **Sweep Efficiency** -- This plot displays one Sweep Efficiency curve for each calculated timestep.
|
||||
This window displays three different graphs describing the overall behavior of the reservoir for each time step from a flow diagnostics point of view.
|
||||
|
||||
- **Lorenz Coefficient** -- This plot displays the Lorenz coefficient for the complete reservoir for each selected time step. The time step color is used as a reference for the time step in the other graphs.
|
||||
- **Flow Capacity vs Storage Capacity** -- This plot displays one curve for each time step of the F-phi curve for the reservoir.
|
||||
- **Sweep Efficiency** -- This plot displays one Sweep Efficiency curve for each selected time step.
|
||||
|
||||
### Settings
|
||||
|
||||
|
||||
|
||||
- **Case** -- Selects the source case for the plot.
|
||||
- **Time Steps** -- These options selects the time steps to be used in the plot.
|
||||
- **All With Calculated FlowDiagnostics** -- Plot data from all the time steps already solved by the Flow Diagnostics Solver, but nothing more. The solver will be run implicitly when the user requests any Flow Diagnostics results on a particular time step using [Cell Results]({{ site.baseurl }}/docs/cellresults), Well Allocation Plots, or [Well Log Extraction Curves]({{ site.baseurl }}/docs/welllogsandplots#well-log-extraction-curves).
|
||||
- **Selected** -- Use the selected time steps only. Activating this options displays a listbox with all the available time steps in the 3D case. Time steps already solved by the Flow Diagnostics Solver are marked with an asterix _`*`_. Select the interesting time steps and press apply to invoke the solver for unsolved time steps, and to show them in the plot.
|
||||
- **Region** -- These group of options controls the cell region of interest for the plot.
|
||||
- **Cell Filter** -- Selects the type of cell filtering to apply. Sub-options are displayed depending on the selection.
|
||||
- **All Active Cells** -- Use all the active cells in the model (default)
|
||||
- **Visible Cells** -- Use the visible cells in a particular predefined view as cell region. This option will respect all the filter settings in the view, and use the correct cell set for each time step.
|
||||
- **View** -- The view to use as cell filter
|
||||
- **Injector Producer Communication** -- The region of communication between selected producers and injectors. See [Flow Diagnostic Results]({{ site.baseurl }}/docs/cellresults#Flow-Diagnostic-Results)
|
||||
- **Tracer Filter** -- Wild card based filter-text to filter the list of tracers
|
||||
- **list** -- Producer and injector tracers to select
|
||||
- **Show Region** -- Button to create (or edit) a 3D View showing the selected region of cells.
|
||||
- **Min communication** -- A threshold for the cells communication value. Cells with communication below this threshold is omitted from the region.
|
||||
- **Flooded by Injector**/**Drained by Producer** -- The region with a Time Of Flight from the selected tracers below the selected threshold.
|
||||
- **Tracer Filter**/_list_/**Show Region** -- See above.
|
||||
- **Max Time of Flight [days]** -- Only cells with a Time of Flight value less then this value are used.
|
||||
- **Options**
|
||||
- **Legend** -- Toggles the legend on/off
|
||||
- **Aquifer Cell Threshold** -- This threshold can be used to exclude unwanted effects of aquifers. Cells are excluded if their pore volume are larger than threshold _`*`_ total pore volume.
|
||||
|
||||
|
||||
@ -1,12 +1,16 @@
|
||||
---
|
||||
layout: docs
|
||||
title: Formations
|
||||
title: Zonations/Formations
|
||||
permalink: /docs/formations/
|
||||
published: true
|
||||
---
|
||||
|
||||
|
||||
|
||||
This section will describe how to use formations for different k-layers of a case, and how to use well picks/zonations for ranges of measured depths of a well path.
|
||||
|
||||
## Formations for k-layers
|
||||
|
||||
Formation information can be utilized in ResInsight as cell colors, used in property filters and are displayed in the **Result info** panel when selecting single cells.
|
||||
|
||||
To use this functionality you will need to :
|
||||
@ -14,7 +18,7 @@ To use this functionality you will need to :
|
||||
1. Import one or more Formation Names file(s)
|
||||
2. Select the correct Formation Names file in the Case of interest
|
||||
|
||||
## Import of Formation Names files
|
||||
### Import of Formation Names Files
|
||||
|
||||
Formation Names files can be imported by using the command: **File->Import->Import Formation Names**.
|
||||
The user is asked to select _`*.lyr`_ files for import.
|
||||
@ -31,25 +35,92 @@ Formation Names files consists of a list of formation names and their k-range. B
|
||||
'Last Name' 21 - 21
|
||||
```
|
||||
|
||||
## Select the Formation file in a Case
|
||||
To make the Formation information available for viewing, you have to select which of the Formation files to be used for a particular case.
|
||||
### Select the Formation File in a Case
|
||||
|
||||
If only one formation file is imported, the formation will automatically be set in the active view's case. If more than one formation file is imported at once, or if a case must change formation file, the formation file for a case can be set later on. This option is available in the **Property Editor** for a case. The formation is selected in the combo box for property **Formation Names File**.
|
||||
|
||||
|
||||
|
||||
This option is available in the **Property Editor** for a case. The formation is selected in the combo box for property **Formation Names File**.
|
||||
|
||||
### Reload of formation data
|
||||
#### Reload of formation data
|
||||
If the formation file is modified outside ResInsight, the formation data can be imported again by the context menu **Formations->Reload**. This command will import formations for the selected formation files.
|
||||
|
||||
## Viewing the Formation Information
|
||||
### Viewing the Formation Information
|
||||
|
||||
### Formations in 3D view
|
||||
#### Formations in 3D View
|
||||
The formations can be visualized as a result property in **Cell Results**, **Cell Edge Result**, and **Separate Fault Result**. When selected, a special legend displaying formation names is activated.
|
||||
|
||||
### Property filter based on formations
|
||||
#### Property Filter Based on Formations
|
||||
Formation names are available in Property Filters as Result Type **Formation Names**. This makes it easy to filter geometry based on formation specifications.
|
||||
|
||||
See [ Cell Filters ]({{ site.baseurl }}/docs/filters) for details.
|
||||
|
||||
### Picking in 3D view
|
||||
#### Picking in 3D View
|
||||
Picking on a cell being part of a formation will display the formation name in the **Result Info** windows, in addition to other pick info for the cell.
|
||||
|
||||
#### Annotations on Plots
|
||||
Formation can be used to annotate the following plot types:
|
||||
- [Well Log Plots]({{site.baseurl}}/docs/welllogsandplots)
|
||||
- [RFT Plots]({{site.baseurl}}/docs/rftplot)
|
||||
- [PLT Plots]({{site.baseurl}}/docs/pltplot)
|
||||
- [Well Allocation Plots]({{site.baseurl}}/docs/flowdiagnosticsplots)
|
||||
|
||||
|
||||
|
||||
For RFT and PLT Plots, **Zonation/Formation Names** can be found in the plot's **Property Editor**. Tick "Show Formations" and choose the case with the desired formations.
|
||||
|
||||
In Well Log Plots and Well Allocation Plots, **Zonation/Formation Names** can be found in the **Property Editor** for a **Track** or **Branch**. In addition to choosing case, the path to show formations for must also be selected, as each track can have curves with data from more than one path.
|
||||
|
||||
|
||||
|
||||
## Well Picks
|
||||
|
||||
Well Picks can be set for a single well path, defined on measured depths of the well path. Unlike formations for k-layers, formations for a well path can only be used to annotate plots. A well pick can be either a *fluid* or a *formation*.
|
||||
|
||||
### Import of Well Pick Files
|
||||
|
||||
Well Pick files can be imported by using the command: **File->Import->Import Well Picks**.
|
||||
The user is asked to select _`*.csv`_ files for import.
|
||||
|
||||
The imported Well Pick files will be added to their associated well path, if a match on well name can be found. If not, new paths will be created, and they can all be found in **Wells** in the **Project Tree**. The file path of the formations can be found in a well path's **Property Editor**.
|
||||
|
||||
|
||||
|
||||
A Well Pick file is a csv-file, which uses semicolon to separate entries in a table. Below is an example of such a file:
|
||||
|
||||
```
|
||||
Well name; Column name; Unit name; Top MD; Base MD
|
||||
B-3H; FLUID; GAS;2203.2;2317.4
|
||||
B-3H; FLUID; OIL;2317.4;2459
|
||||
B-3H; STRAT; FANGST GP. ;2203.399902;2223.350098
|
||||
B-3H; STRAT; Ile Fm. ;2203.399902;2223.350098
|
||||
B-3H; STRAT; Ile Fm. 3 ;2203.401123;2219.26001
|
||||
B-3H; STRAT; Ile Fm. 2 ;2219.26001;2222.399902
|
||||
B-3H; STRAT; Ile Fm. 2.2 ;2219.26;2219.350098
|
||||
B-3H; STRAT; Ile Fm. 2.1 ;2219.350098;2222.399902
|
||||
B-3H; STRAT; Ile Fm. 1 ;2222.399902;2223.350098
|
||||
B-3H; STRAT; BAAT GP. ;2223.350098;2979.28125
|
||||
B-3H; STRAT; Ror Fm. ;2223.350098;2285.199951
|
||||
B-3H; STRAT; Ror Fm. 2 ;2223.350098;2246
|
||||
B-3H; STRAT; Ror Fm. 1 ;2246;2285.199951
|
||||
B-2H; FLUID; GAS;2144.4;2338.5
|
||||
B-2H; FLUID; OIL;2338.5;2440
|
||||
B-2H; STRAT; FANGST GP. ;2144.199951;2158.389893
|
||||
B-2H; STRAT; Ile Fm. ;2144.199951;2158.389893
|
||||
B-2H; STRAT; Ile Fm. 2 ;2144.201416;2156.197266
|
||||
B-2H; STRAT; Ile Fm. 1 ;2156.197266;2158.38501
|
||||
```
|
||||
|
||||
The file must have the columns "Well name", "Unit name" (i.e. formation name), "Top MD" and "Base MD" (i.e. measured depth) to be regarded as a Well Pick file. They can be listed in any order, and all other columns will be ignorded.
|
||||
|
||||
The three unit names *OIL*, *GAS* and *WATER* are interpreted as *fluids*. Other unit names with only capital letters are *groups*. A unit name without an index is simply a *formation*. Unit names with one number is a *formation 1*, unit names with *one* punctuation is a *formation 2*, two punctuations, *formation 3* and so on. Indentions in column name will be ignored.
|
||||
|
||||
### Viewing the Well Picks
|
||||
See [Annotations on plots](#annotations-on-plots). Annotations are added to plots in the same way as for k-layered formations, but the source is different.
|
||||
|
||||
|
||||
|
||||
In the **Property Editor**, choose **Well Path** as **Source**, and all well paths with formations will be shown in the drop-down list below. All disjoint well picks for the chosen well path is shown on default. To reduce the number of annotations, the **Well Pick Filter** can be used.
|
||||
|
||||
|
||||
|
||||
The **Well Pick Filter** will show formations down to the specified level. If more there are more than one formation within 0.1m of an MD, only the lowermost formation is shown. Well picks interpreted as *Fluids* are only shown by ticking the **Show Fluids** mark.
|
||||
|
||||
@ -5,7 +5,7 @@ permalink: /docs/gettingstarted/
|
||||
published: true
|
||||
---
|
||||
|
||||
### User interface overview
|
||||
### User Interface Overview
|
||||
|
||||
ResInsight has two main windows. One for 3D related visualization, and one for 2D graphs and plots. These ares shown in the images below.
|
||||
|
||||
@ -15,7 +15,7 @@ ResInsight has two main windows. One for 3D related visualization, and one for 2
|
||||
##### Plot Main Window
|
||||
|
||||
|
||||
#### Switching between the two main windows
|
||||
#### Switching Between the Two Main Windows
|
||||
|
||||
The two main windows has a toolbar button each, that directly opens and raises the other window.
|
||||
|
||||
@ -61,7 +61,7 @@ Commands to arrange the windows in the standard ways are available from the **Wi
|
||||
- **Cascade Windows** -- organize all open view windows slightly offset on top of each other
|
||||
- **Close All Windows** -- close all open view windows
|
||||
|
||||
#### Editing 3D views and Plot Windows content
|
||||
#### Editing 3D Views and Plot Windows Content
|
||||
|
||||
Most of the settings and features of ResInsight is accessible through the **Project Tree** and the **Property Editor**. Selecting an item in the **Project Tree** activates the corresponding Window, and shows the item properties in the **Property Editor** available for editing.
|
||||
|
||||
@ -72,22 +72,22 @@ Context menu commands are also available to do special operations on a selected
|
||||
How to interact and manipulate the 3D model is described in [Model Navigation]({{ site.baseurl }}/docs/modelnavigation)
|
||||
|
||||
|
||||
### Cases and their types
|
||||
### Cases and Their Types
|
||||
|
||||
A *Case* in ResInsight means a Grid model with a particular set of results or property data. There are three different types of Eclipse cases and one type of Geomechanical cases.
|
||||
|
||||
#### Eclipse Cases
|
||||
There are three different Eclipse Case types:
|
||||
|
||||
##### Result case 
|
||||
##### Result Case 
|
||||
This is a Case based on the results of an Eclipse simulation, read from a grid file together with static and restart data. Multiple Cases can be selected and read from a folder.
|
||||
|
||||
##### Input case 
|
||||
##### Input Case 
|
||||
This Case type is based on a _`*.GRDECL`_ file, or a part of an Eclipse *Input* file. This Case type supports loading single ASCII files defining Eclipse Cell Properties, and also to export modified property sets to ASCII files.
|
||||
Each of the Eclipse properties are listed as separate entities in the **Project Tree**, and can be renamed and exported.
|
||||
See [ Grid Import and Property Export ]({{ site.baseurl }}/docs/gridimportexport)
|
||||
|
||||
##### Statistics case 
|
||||
##### Statistics Case 
|
||||
This is a Case type that belongs to a *Grid Case Group* and makes statistical calculations based on the source cases in the Grid Case Group. See [ Grid Case Groups and Statistics ]({{ site.baseurl }}/docs/casegroupsandstatistics).
|
||||
|
||||
##### Summary Case 
|
||||
@ -103,7 +103,7 @@ There are only one type of geomechanical cases, namely the ABAQUS-odb case type.
|
||||
A **Grid Case Group** is a group of Eclipse **Result Cases** with identical grids, but generally different active cells, initial values and results. These cases are called *Source Cases*. The purpose of a Grid Case group is to make it easy to calculate statistics across the source cases both for static and dynamic Eclipse Properties. See [ Grid Case Groups and Statistics ]({{ site.baseurl }}/docs/casegroupsandstatistics).
|
||||
|
||||
|
||||
### The Project file and the Cache directory
|
||||
### The Project File and the Cache Directory
|
||||
|
||||
ResInsight stores all the views and settings in a Project File with the extension: _`*.rsp`_.
|
||||
This file only contains *references* to the real data files, and does not in any way copy the data itself. Data files generated by ResInsight are also referenced from the Project File.
|
||||
|
||||
@ -5,7 +5,7 @@ permalink: /docs/gridimportexport/
|
||||
published: true
|
||||
---
|
||||
|
||||
## Importing Eclipse cases
|
||||
## Importing Eclipse Cases
|
||||
ResInsight supports the following type of Eclipse input data:
|
||||
|
||||
- _`*.GRID`_ and _`*.EGRID`_ files along with their _`*.INIT`_ and restart files _`*.XNNN`_ and _`*.UNRST`_.
|
||||
@ -21,19 +21,48 @@ The **Reload Case** command can be used to reload a previously imported case, to
|
||||
You can select several grid files in one go by multiple selection of files (Ctrl + left mouse button, Shift + left mouse button).
|
||||
</div>
|
||||
|
||||
#### Result Index File
|
||||
|
||||
### Eclipse ASCII input data
|
||||
If enabled, ResInsight will generate an index file when reading the eclipse result files for the first time. This file will significantly reduce the time used to open the case next time. The file is named _`<casename>.RESINSIGHT_IDX`_
|
||||
See [Preferences: Behavior When Loading Data]({{ site.baseurl }}/docs/preferences#behavior-when-loading-data)
|
||||
|
||||
### Time Step Filtered Eclipse Result
|
||||
Some Eclipse files have an enormous amount of time steps. If only a selection of the time steps really are needed for the session, the time steps can be filtered before loading. This can possibly speed up the import a great deal. Filtering can be done in the following way.
|
||||
|
||||
Select **File->Import->  Import Eclipse Case (Time Step Filtered)** and select an _`*.EGRID`_ or _`*.GRID`_ Eclipse file for import. A dialog will appear.
|
||||
|
||||
|
||||
|
||||
Filtering can be done by adjusting the following parameters:
|
||||
* First and last time step
|
||||
* Step filter type and with step interval size
|
||||
|
||||
First and last time step to include in the import can be chosen in their respective drop down list. All time steps found in the file are included in both lists.
|
||||
|
||||
**Filter Type** is set to *All* by default. This means that all time steps between the first and last chosen time step will be imported. The alternative to *All* is to skip time steps in a number of *Days*, *Weeks*, *Months*, *Quarters* or *Years*. The skipping interval is set in the text field below. After editing the **Interval** field, press *tab* to update the **Filtered Time Steps** preview, or click anywhere in the dialog. Click *Ok* to import when the filter is ready.
|
||||
|
||||
Filtering can also be done after import, in a case's **Property Window**.
|
||||
|
||||
|
||||
|
||||
After clicking *Reload Case*, the time steps in the toolbar will be updated.
|
||||
|
||||
### Eclipse ASCII Input Data
|
||||
1. Select **File->Import->  Import Input Eclipse Case** and select a _`*.GRDECL`_ file.
|
||||
2. The case is imported, and a view of the case is created
|
||||
3. Right-click the **Input Properties** in the generated **Input Case** and use the context menu to import additional Eclipse Property data files.
|
||||
|
||||
### Handling missing or wrong MAPAXES
|
||||
### Handling Missing or Wrong MAPAXES
|
||||
|
||||
The X and Y grid data can be negated in order to make the Grid model appear correctly in ResInsight. This functionality is accessible in the **Property Editor** for all Eclipse Case types as the toggle buttons **Flip X Axis** and **Flip Y Axis** as shown in the example below.
|
||||
|
||||
|
||||
|
||||
## Importing ABAQUS odb cases
|
||||
### SourSimRL Import
|
||||
|
||||
Results From the simulation software SourSimRL can be imported using the **SourSim File Name** field. Importing such a file will enable result type called **SourSimRL** as explained in [Eclipse Result Types]({{ site.baseurl }}/docs/cellresults#eclipse-result-types)
|
||||
|
||||
## Importing ABAQUS Odb Cases
|
||||
When ResInsight is compiled with ABAQUS-odb support, _`*.odb`_ files can be imported by selecting the command:
|
||||
|
||||
**File->Import->  Import Geo Mechanical Model**
|
||||
|
||||
45
docs/GridStatisticsDialog.md
Normal file
45
docs/GridStatisticsDialog.md
Normal file
@ -0,0 +1,45 @@
|
||||
---
|
||||
layout: docs
|
||||
title: Grid Statistics Dialog
|
||||
permalink: /docs/gridstatisticsdialog/
|
||||
published: true
|
||||
---
|
||||
|
||||
|
||||
ResInsight 3D Views has an [info box]({{ site.baseurl }}/docs/reservoirviews#info-box) in the upper right corner displaying statistics for the current view. A more detailed version of this information may also be displayed in a separate dialog window. Right click on the 3D view background and select **Grid Statistics** to bring up the dialog.
|
||||
|
||||
## Grid Statistics Dialog Fields
|
||||
The dialog consist of three information parts.
|
||||
- Info text
|
||||
- Histogram
|
||||
- Cumulative Histogram
|
||||
|
||||
### Info Text
|
||||
The Info Text field shows general info about the case, the selected results, and some statistics.
|
||||
|
||||
### Histogram
|
||||
The histogram shows a histogram of the complete time series of the currently loaded Cell Result together with:
|
||||
- The mean value ( a blue line )
|
||||
- P10 and P90 ( red lines )
|
||||
|
||||
### Cumulative Histogram
|
||||
The cumulative histogram shows av accumulated version of the histogram above.
|
||||
|
||||
## Grid Statistics Configuration
|
||||
A grid statistics dialog is always connected to the 3D view from where it was opened. When the contents of the 3D view changes due to user interactions, the grid statistics dialog contents will be updated automatically along with the info box. The info box has some options for configuration. These settings become available by clicking in the info box or the info box node in the project tree.
|
||||
|
||||
|
||||
|
||||
The options in the Visibility group apply to the info box only and do not affect the Grid Statistics dialog, while the options in the Statistics Options group affect both.
|
||||
|
||||
### Statistics Options
|
||||
- **Statistics Time Range** -– Controls whether all time steps or only the current time step are included when statistics is computed. Flow Diagnostic results can only use the current time step option.
|
||||
- **Statistics Cell Range** -– Controls if visible cells or all active cells is included when statistics is computed.
|
||||
|
||||
## Snapshot
|
||||
The Grid Statistics dialog has a toolbar containing two buttons for snapshot functionality. The leftmost button copies a snapshot of the dialog contents to the operating system's clipboard, while the rightmost button creates a file containing the snapshot.
|
||||
|
||||
<div class="note">
|
||||
The main window also has a snapshot toolbar containing the button <a href="{{ site.baseurl }}/docs/snapshots#snapshot-all-viewsplots-to-file-">Snapshot All Views</a>. This button will include a snapshot of the Grid Statistics dialog if opened.
|
||||
</div>
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
layout: docs
|
||||
title: ResInsight 2017.05
|
||||
title: ResInsight 2018.01
|
||||
permalink: /docs/home/
|
||||
published: true
|
||||
---
|
||||
@ -18,7 +18,7 @@ Flow diagnostics calculations are embedded in the user interface and allows inst
|
||||
### Octave Integration
|
||||
Integration with GNU Octave enables powerful and flexible result manipulation and computations. Derived results can be returned to ResInsight for further handling and visualization. Eventually, derived and computed properties can be directly exported to Eclipse input formats for further simulation cycles and parameter studies.
|
||||
|
||||
### Data support
|
||||
### Data Support
|
||||
The main input data is
|
||||
_`*.GRID`_ and _`*.EGRID`_ files along with their _`*.INIT`_ and restart files _`*.XNNN`_ and _`*.UNRST`_.
|
||||
Summary vectors can be imported from _`*.SMSPEC`_ files.
|
||||
|
||||
33
docs/ImportObsTimeHistData.md
Normal file
33
docs/ImportObsTimeHistData.md
Normal file
@ -0,0 +1,33 @@
|
||||
---
|
||||
layout: docs
|
||||
title: Import Observed Time History Data
|
||||
permalink: /docs/importobstimehistdata/
|
||||
published: true
|
||||
---
|
||||
|
||||
Importing observed time history data to ResInsight may be performed in two different ways:
|
||||
- By selecting the main menu item **File -> Import -> Import Observed Time History Data**
|
||||
- By using the context command **Import Observed Time History Data** on the **Observed Time History Data** item in the **Plot Main Window Project Tree**
|
||||
|
||||
The following file types are supported:
|
||||
- RSM observed time history data file (_\*.rsm_)
|
||||
- Column based (Comma Separated Values, CSV) time history data file (_\*.csv/\*.txt_)
|
||||
|
||||
## Import RSM observed time history data
|
||||
To import RSM files, the only action needed from the user is to select one or more RSM files. When the import is finished, one tree node for each file will appear under the **Observed Time History Data** node in the project tree.
|
||||
|
||||
## Import CSV/txt observed time history data
|
||||
CSV/txt files are generic ascii files which may have slightly different formatting. When importing these types of files the user is presented a dialog, where the user may tell ResInsight how to import the selected file(s). If more than one file is selected, the dialog appears once for each file.
|
||||
|
||||
### CSV/txt import options dialog
|
||||
|
||||
|
||||
Dialog fields description:
|
||||
- **Cell Separator** -- Select the correct cell separator character. ResInsight will try to set the correct value as default.
|
||||
- **Decimal Separator** -- Select the correct decimal separator. ResInsight will try to set the correct value as default.
|
||||
- **Selected Time Column** -- Select the column that contains the time/date information. The first column is default.
|
||||
- **Use Custom Date Time Format** -- Check this box if the Date Format and/or Time Format in the file do not match any of the most common formats.
|
||||
- **Custom Date Time Format** -- Enter date time format to match the time information in the file. This field is visible only when the above check box checked. A tooltip will tell the user how to enter the correct information.
|
||||
- **Date Format** -- Select the date format matching the date information in the file.
|
||||
- **Time Format** -- Select the time format matching the time information in the file. If the file contains dates only, this field is ignored by ResInsight.
|
||||
- **Preview** -- Preview the first 30 lines of the file contents. The view will reflect the currently selected Cell Separator and the selected time column is marked in yellow.
|
||||
@ -8,14 +8,14 @@ published: true
|
||||
|
||||
<small>Note: None of the binary distributions includes support for ABAQUS odb files.</small>
|
||||
|
||||
### ResInsight installation
|
||||
### ResInsight Installation
|
||||
|
||||
1. Download ZIP binary distribution from [https://github.com/OPM/ResInsight/releases](https://github.com/OPM/ResInsight/releases "release section on GitHub")
|
||||
2. Extract content from ZIP file
|
||||
3. Start ResInsight.exe
|
||||
|
||||
### Octave installation (optional)
|
||||
1. Download [Octave-4.0.0](ftp://ftp.gnu.org/gnu/octave/windows/octave-4.0.0_0-installer.exe) and install it.
|
||||
### Octave Installation (optional)
|
||||
1. Download [Octave-4.0.0](ftp://ftp.gnu.org/gnu/octave/windows) and install it. (Newer versions will not work)
|
||||
2. Launch ResInsight.exe, open **Edit->Preferences**.
|
||||
3. On the **Octave** tab, enter the path to the Octave command line interpreter executable.
|
||||
( Usually _`C:\Your\Path\To\Octave-x.x.x\bin\octave-cli.exe`_ )
|
||||
|
||||
@ -8,16 +8,16 @@ published: true
|
||||
<small>Note: None of the binary distributions includes support for ABAQUS odb files.</small>
|
||||
|
||||
|
||||
### ResInsight installation
|
||||
### ResInsight Installation
|
||||
|
||||
1. Download TAR.GZ binary distribution from [https://github.com/OPM/ResInsight/releases](https://github.com/OPM/ResInsight/releases "release section on GitHub")
|
||||
2. Extract content from TAR file
|
||||
3. Start ./ResInsight
|
||||
|
||||
### Installation from binary packages on Linux
|
||||
### Installation from Binary Packages on Linux
|
||||
Packages for ResInsight are available as part of the distribution by the [Opm project](http://opm-project.org/?page_id=36)
|
||||
|
||||
### Octave installation (optional)
|
||||
### Octave Installation (optional)
|
||||
The precompiled octave support is only tested for RedHat 6 (ResInsight 1.3.2-dev and earlier, was also tested on RedHat 5) and is not expected to work for other configurations, unless you build ResInsight yourself. See [Build Instructions]({{ site.baseurl }}/docs/buildinstructions)
|
||||
|
||||
1. Install Octave directly from the package manager in Linux. See the documentation for your particular distribution.
|
||||
@ -25,7 +25,7 @@ The precompiled octave support is only tested for RedHat 6 (ResInsight 1.3.2-dev
|
||||
3. Enter the path to the Octave command line interpreter executable.
|
||||
( usually just _`octave`_. )
|
||||
|
||||
### Display menu icons in GNOME
|
||||
### Display Menu Icons in GNOME
|
||||
By default, icons are not visible in menus in the GNOME desktop environment. ResInsight has icons for many menu items, and icons can be set visible by issuing the following commands (Tested on RHEL6) :
|
||||
|
||||
```
|
||||
|
||||
@ -9,17 +9,17 @@ published: true
|
||||
|
||||
Intersections are cross sections of the grid model that displays the grid cell values on planes that cut through the grid in various ways.
|
||||
|
||||
There are two main types of intersections. The first one which simply is called **Intersection** is defined by a picewise linear curve and an extrusion direction. The curve can be either a Simulation Well, a Well Path or a user defined polyline. The second intersection type is called an **Intersection Box** that can be used both as a box cutting the grid cells, or collapsed to a restricted axis aligned plane.
|
||||
There are two main types of intersections. The first one which simply is called **Intersection**, is defined by a piecewise linear curve and an extrusion direction. The curve can be either a Simulation Well, a Well Path, a user defined polyline, or a user defined line. The second intersection type is called an **Intersection Box**. An Intersection Box can be used as a box cutting the grid cells, or collapsed to a restricted axis aligned plane.
|
||||
|
||||
Intersections are stored in a folder named **Intersections** in a **View** as shown below.
|
||||
All types of intersections are stored in a folder named **Intersections** in a **View** as shown below.
|
||||
|
||||
|
||||
|
||||
## Curve Based **Intersections**
|
||||
|
||||
There are three types of curve based intersections: Well Path, Simulation Well, and Polyline intersections.
|
||||
There are four types of curve based intersections: Well Path, Simulation Well, Polyline, and Azimuth and Dip. Azimuth and Dip differs from the other three curves, as it is defined just by one straight line. It is called Azimuth and Dip because the plane's extrusion direction can be defined by the two angles.
|
||||
|
||||
Any of these can be created by activating  **New Intersection** from the context menu of the **Intersections** item in the Project Tree.
|
||||
Any of these intersections can be created by activating  **New Intersection** from the context menu of the **Intersections** item in the Project Tree.
|
||||
|
||||
They can also be created from the context menu in the 3D view, as described below.
|
||||
|
||||
@ -27,17 +27,17 @@ They can also be created from the context menu in the 3D view, as described belo
|
||||
To be able to see the intersections in the 3D view, the grid cells can be hidden by disabling the <b>Grids</b> item in the Project Tree or activating the <b>Hide Grid Cells</b> toolbar button.
|
||||
</div>
|
||||
|
||||
### Common Curve based Intersection Options
|
||||
### Common Curve Based Intersection Options
|
||||
|
||||
The property panel of a Well Path based Intersection is shown below:
|
||||
The property panel of a well path based intersection is shown below:
|
||||
|
||||
|
||||
|
||||
- **Name** -- Automatically created based on the item specifying the intersection. The user can customize the name by editing, but will be updated if you change the well or well path.
|
||||
- **Intersecting Geometry** -- These options controls the curve to be used for the cross section, and depends on the type of intersection you choose.
|
||||
- **Direction** -- Horizontal, vertical or Defined by two points
|
||||
- **Extent length** -- Defines how far an intersection for Well Path or Simulation Well is extended at intersection ends
|
||||
- **Show Inactive Cells** -- Controls if inactive cells are included when creating the intersection geometry
|
||||
- **Direction** -- Horizontal, vertical or defined by two points.
|
||||
- **Extent Length** -- Defines how far an intersection for well path or simulation Well is extended at intersection ends.
|
||||
- **Show Inactive Cells** -- Controls if inactive cells are included when creating the intersection geometry.
|
||||
|
||||
#### Direction
|
||||
|
||||
@ -45,7 +45,7 @@ The direction defined is used to extrude the curve in the defined direction, and
|
||||
|
||||
When selection the **Horizontal** option, the start and end point of the curve is used as a baseline, and the horizontal direction is thus perpendicular to that line.
|
||||
|
||||
When **Defined by two points** is the active option, the user can define the direction based on any two points. The direction from from the first to the second point defines the extrude direction.
|
||||
When **Defined by two points** is the active option, the user can define the direction based on any two points. The direction from the first to the second point defines the extrude direction.
|
||||
|
||||
- The background color of this list is set to light pink when adding points by picking in the 3D view is active.
|
||||
- To finish adding points, click the button **Stop picking points** in the **Property Editor**.
|
||||
@ -68,6 +68,7 @@ When a simulation well intersection is created, the source simulation well can b
|
||||
If the well contains more than one branch, the intersection geometry will be created for the selected branch in the **Branch** combo box.
|
||||
|
||||
### Polyline Intersection
|
||||
|
||||
A new **Polyline** intersection can be created from the context menu in the 3D view. Then, by left-clicking on reservoir geometry, a polyline is created. The points are added to the point list in the **Property Editor**.
|
||||
|
||||
|
||||
@ -76,11 +77,34 @@ A new **Polyline** intersection can be created from the context menu in the 3D v
|
||||
- To finish adding points, click the button **Stop picking points** in the **Property Editor**.
|
||||
- The background color of the point list is then set to white.
|
||||
|
||||
The points in the list can be deleted and edited using the keyboard.
|
||||
To append more points by clicking in the 3D view, push the button **Start picking points** again.
|
||||
The points in the list can be deleted and edited using the keyboard. To append more points (by clicking in the 3D view), push the button **Start picking points** again.
|
||||
|
||||
The points in the list can be copied to clipboard using **CTRL-C** when keyboard focus is inside the point list. A new list of points can be pasted into the point list by using **CTRL-V**.
|
||||
|
||||
### Azimuth and Dip
|
||||
|
||||
A new **Azimuth and Dip** intersection can be created from the context menu in the 3D view. Then, by left-clicking two points on reservoir geometry, a single line is created between the first point, and the second point projected down to the plane with same z-value as the first point. The two points are added to the point list in the **Property Editor**.
|
||||
|
||||
|
||||
|
||||
- The background color of this list is set to light pink when adding points by picking in the 3D view is active.
|
||||
- To finish adding points, click the button **Stop picking points** in the **Property Editor**.
|
||||
- The background color of the point list is then set to white.
|
||||
|
||||
The points in the list can be deleted and edited using the keyboard. To append more points by clicking in the 3D view, push the button **Start picking points** again.
|
||||
|
||||
The points in the list can be copied to clipboard using **CTRL-C** when keyboard focus is inside the point list. A new list of points can be pasted into the point list by using **CTRL-V**.
|
||||
|
||||
When two points are picked, a plane between the points will appear in the 3D view, with a 90 degrees **Dip**, and the **Azimuth** angle calculated from the two points. The two angles can be edited in the **Property Editor** of the intersection, and is defined by the following:
|
||||
- **Dip** is the angle between the horizontal plane and down.
|
||||
- **Azimuth** is the angle between North and the plane. Changing the azimuth will rotate the plane about the first point picked in the 3D view.
|
||||
|
||||
The length of the plane can also be set manually in the **Property Editor**.
|
||||
- **Length Up** is the distance from the user defined horizontal line, to the top of the plane intersecting the model.
|
||||
- **Length Down** is the distance from the user defined horizontal line, to the bottom of the plane intersecting the model.
|
||||
|
||||
|
||||
|
||||
## Intersection Box and Intersection Planes
|
||||
|
||||
A new **Intersection Box** or **Intersection Plane** can be created from the context menu in the 3D view or the context menu in the **Project Tree**.
|
||||
|
||||
14
docs/LatexEquations.txt
Normal file
14
docs/LatexEquations.txt
Normal file
@ -0,0 +1,14 @@
|
||||
Equations can be stored as png images using http://latex2png.com/
|
||||
Resoluton 200 and colour FFFFFF has been used when saving pngs
|
||||
|
||||
Equations from Completions
|
||||
|
||||
Perforation Intervals
|
||||
|
||||
K = \sqrt{K_Y K_Z}
|
||||
|
||||
r_{0_X} = 0.28 \frac{ \sqrt{ D_z^2 \sqrt{\frac{K_Y}{K_Z}} + D_y^2 \sqrt{\frac{K_Z}{K_Y}} } }{\sqrt[4]{\frac{K_y}{K_z}} + \sqrt[4]{\frac{K_z}{K_y}}}
|
||||
|
||||
T_X = \frac{c 2 \pi K l_x }{\ln (\frac{r_{0_x}}{r_w}) + S}
|
||||
|
||||
T = \sqrt{T_x + T_y + T_z}
|
||||
@ -15,7 +15,7 @@ To establish a link between views, select 
|
||||
|
||||
## Linked view Options
|
||||
## Linked View Options
|
||||
|
||||
When selecting a linked view in the project tree, the different options are available in the **Property Editor**.
|
||||
|
||||
@ -27,7 +27,7 @@ When selecting a linked view in the project tree, the different options are avai
|
||||
- **Show Cursor** -- Shows the position of the mouse cursor in the other views as a cross-hair
|
||||
- **Time Step** -- Change of time step in any of the views where this option is active will be applied to the other linked views with this option set.
|
||||
- **Cell Color Result** -- Change of cell result in the master view will be applied to all dependent views where this option is active. **Cell Color Result** is only supported between views of the *same type*.
|
||||
- **Legend Definition** -- Links the legend between views already linking the **Cell Results Color**
|
||||
- **Legend Definition** -- Links the legend between views already linking the **Cell Results Color**.
|
||||
|
||||
#### Link Cell Filters
|
||||
|
||||
@ -42,17 +42,17 @@ A linked view can temporarily be disabled by unchecking the linked view. To disa
|
||||
|
||||
Right-clicking one of the linked view entries in the **Project Tree** displays the following menu entries:
|
||||
|
||||
- **Open All Linked Views** -- Open all the views which is part of the linked view group
|
||||
- **Open All Linked Views** -- Open all the views which is part of the linked view group.
|
||||
- **Delete All Linked Views** -- Delete the linked views group, and thereby unlink all the views.
|
||||
- **Delete** -- Remove an individual view from the group of linked views
|
||||
- **Delete** -- Remove an individual view from the group of linked views.
|
||||
|
||||
## 3D view Context menu
|
||||
## 3D View Context Menu
|
||||
To activate the menu items for a linked view, right-click inside the 3D view anywhere outside the model.
|
||||
Depending on whether the view is a dependent-, or an unlinked view, some of the following commands are available:
|
||||
|
||||
- **Show Link Options** -- Activate the linked view item in the project tree, and show its properties.
|
||||
- **Set As Master View** -- Use the view as Master View
|
||||
- **Link View** -- Add the view to list of linked views
|
||||
- **Unlink View** -- Delete the view from list of linked views
|
||||
- **Set As Master View** -- Use the view as Master View.
|
||||
- **Link View** -- Add the view to list of linked views.
|
||||
- **Unlink View** -- Delete the view from list of linked views.
|
||||
|
||||
Master views have no available linking commands.
|
||||
|
||||
@ -11,7 +11,7 @@ ResInsight comes with four navigation modes. The active mode can be selected in
|
||||
|
||||
Note that changing the navigation mode applies to the currently active view only, and views created after the change.
|
||||
|
||||
These abbrevitations are used in the tables below:
|
||||
These abbreviations are used in the tables below:
|
||||
|
||||
|Abbreviation | Meaning |
|
||||
|-------------|---------|
|
||||
|
||||
154
docs/ObservedData.md
Normal file
154
docs/ObservedData.md
Normal file
@ -0,0 +1,154 @@
|
||||
---
|
||||
layout: docs
|
||||
title: Observed Time History Data
|
||||
permalink: /docs/observeddata/
|
||||
published: true
|
||||
---
|
||||
|
||||
Observed Time History Data, is data measured in time. On import of observed time history data, ResInsight translates the data to make it similar to summary data. Observed time history data can be plotted along with summary data in **Summary Plots**.
|
||||
|
||||
## Import Observed Time History Data
|
||||
Importing observed time history data to ResInsight may be performed in two different ways:
|
||||
- By selecting the main menu item **File -> Import -> Import Observed Time History Data**
|
||||
- By using the context command **Import Observed Time History Data** on the **Observed Time History Data** item in the **Plot Main Window Project Tree**
|
||||
|
||||
The following file types are supported:
|
||||
- RSM observed time history data file (_\*.rsm_)
|
||||
- Column based (Comma Separated Values, CSV) time history data file (_\*.csv/\*.txt_)
|
||||
The imported  Observed Time History Data files will be added to **Observed Time History Data**.
|
||||
|
||||
See [Import Observed Time History Data]({{site.baseurl}}/docs/importobstimehistdata) for details.
|
||||
|
||||
Which summaries that has been detected in a Observed Time History Data file can be read in an Observed Time History Data's **Property Editor**. In the image below, time and year info has been found together with the summary "WBP9L" for the well "OP-1".
|
||||
|
||||
|
||||
|
||||
## File Formats
|
||||
|
||||
### Import CSV/txt Observed Time History Data
|
||||
CSV/txt files are generic ascii files which may have slightly different formatting. When importing these types of files the user is presented a dialog, where the user may tell ResInsight how to import the selected file(s). If more than one file is selected, the dialog appears once for each file.
|
||||
|
||||
#### CSV/txt Import Options Dialog
|
||||
|
||||
|
||||
Dialog fields description:
|
||||
- **Cell Separator** -- Select the correct cell separator character. ResInsight will try to set the correct value as default.
|
||||
- **Decimal Separator** -- Select the correct decimal separator. ResInsight will try to set the correct value as default.
|
||||
- **Selected Time Column** -- Select the column that contains the time/date information. The first column is default.
|
||||
- **Use Custom Date Time Format** -- Check this box if the Date Format and/or Time Format in the file do not match any of the most common formats.
|
||||
- **Custom Date Time Format** -- Enter date time format to match the time information in the file. This field is visible only when the above check box checked. A tooltip will tell the user how to enter the correct information.
|
||||
- **Date Format** -- Select the date format matching the date information in the file.
|
||||
- **Time Format** -- Select the time format matching the time information in the file. If the file contains dates only, this field is ignored by ResInsight.
|
||||
- **Preview** -- Preview the first 30 lines of the file contents. The view will reflect the currently selected Cell Separator and the selected time column is marked in yellow.
|
||||
|
||||
### Import RSM observed time history data
|
||||
To import RSM files, the only action needed from the user is to select one or more RSM files. When the import is finished, one tree node for each file will appear under the **Observed Time History Data** node in the project tree. RSM files can be either *Column based* or *Keyword based*.
|
||||
|
||||
#### Column Based File Format
|
||||
|
||||
If a column based file is presented, ResInsight first tries to identify if its header has fixed width or not. Further, the header is interpreted by looking for specific lines.
|
||||
|
||||
The first line must have one or more vector mnemonics. The initial letter(s) in a mnemonic specify which summary data type the column represents. For instance, *FVPT* and *FWPT* are of type *Field*, as they both have an initial *F*. *WWCTH* and *WGORH* are well data types. See *Vector naming convention* in **Eclipse: File Formats Reference Manual** for a full overview of supported mnemonics.
|
||||
|
||||
The next lines can define units, well/group names, region names, LGR names and block numbers and the local cell number. They do not have to appear in any particular order. Scale factors can also be included, but will be ignored by ResInsight. All lines starting with _*--*_ will also be ignored.
|
||||
|
||||
##### Column Based with Fixed Header Width
|
||||
|
||||
When interpreting column based files with fixed header width, ResInsight looks for left aligned column entries. These type of files are interpreted as we naturally read them. More than one table can be present in each file.
|
||||
|
||||
```
|
||||
1
|
||||
-------------------------------------------------------------------------
|
||||
SUMMARY
|
||||
-------------------------------------------------------------------------
|
||||
DATE FGIRH FVPT FWPT FOPT FLPT
|
||||
SM3/DAY RM3 SM3 SM3 SM3
|
||||
*10**3 *10**3 *10**3 *10**3
|
||||
|
||||
|
||||
-------------------------------------------------------------------------
|
||||
6-NOV-1997 0 0 0 0 0
|
||||
7-NOV-1997 0 5.749954 0.004548 4.379801 4.384350
|
||||
8-NOV-1997 0 13.76883 0.010841 10.48852 10.49936
|
||||
9-NOV-1997 0 19.38692 0.015243 14.76847 14.78372
|
||||
10-NOV-1997 0 24.07161 0.018914 18.33751 18.35642
|
||||
11-NOV-1997 0 28.79427 0.022613 21.93558 21.95819
|
||||
```
|
||||
|
||||
##### Column Based with Random Header Width
|
||||
|
||||
Column Based with Random Header Width will try to be parsed in the same way as fixed width, but it might fail in situations like the one below. We can see that SM3/SM3 *probably* belongs to WGORH, but it is parsed to WWCTH, as it is the second entry on that line.
|
||||
|
||||
```
|
||||
TIME WWCTH WGORH
|
||||
DAYS SM3/SM3
|
||||
|
||||
A-5HP A-5HP
|
||||
1 0.000 0.000
|
||||
2 0.000 0.000
|
||||
3 0.000 0.000
|
||||
```
|
||||
|
||||
#### Keyword Based File Format
|
||||
|
||||
If the non-comment line includes the word "VECTOR", the file is interpreted as a keyword based file. In keyword based files, the content of the one-column tables is described in each header. Tables should be associated with a table containing time stamps. In the example below, *S-1AH-GOR* is associated with *YEARX*, since their origin is equal. ResInsight always interpret *ORIGIN* as well name, and look for a table with the line "VECTOR YEARX" to associate with it.
|
||||
|
||||
```
|
||||
----------------------------------------------
|
||||
-- GOR data
|
||||
----------------------------------------------
|
||||
VECTOR S-122AH-GOR
|
||||
UNITS SM3/SM3
|
||||
ORIGIN GORS-122AH
|
||||
330.6601
|
||||
257.7500
|
||||
335.9894
|
||||
301.4388
|
||||
260.4193
|
||||
306.0298
|
||||
280.2883
|
||||
|
||||
VECTOR YEARX
|
||||
ORIGIN GORS-112AH
|
||||
UNITS YEAR
|
||||
1999.7902
|
||||
1999.8446
|
||||
1999.9285
|
||||
2000.0391
|
||||
2000.0800
|
||||
2000.0862
|
||||
2000.1285
|
||||
---comment
|
||||
|
||||
|
||||
----------------------------------------------
|
||||
-- GOR data
|
||||
----------------------------------------------
|
||||
VECTOR S-211H-GOR
|
||||
UNITS SM3/SM3
|
||||
ORIGIN GORS-211H
|
||||
293.8103
|
||||
293.1634
|
||||
304.0000
|
||||
334.5932
|
||||
306.4610
|
||||
293.7571
|
||||
|
||||
VECTOR YEARX
|
||||
ORIGIN GORS-22H
|
||||
UNITS YEAR
|
||||
1999.8255
|
||||
2000.1274
|
||||
2000.2075
|
||||
2000.2367
|
||||
2000.4033
|
||||
2000.4966
|
||||
```
|
||||
|
||||
Please seek "User data file formats" in **Eclipse: File Formats Reference Manual** for details.
|
||||
|
||||
## Viewing Observed Time History Data
|
||||
|
||||
|
||||
|
||||
To plot Observed Time History Data, choose **New Summary Plot** in the context menu of **Summary Plots**, in **Plot Object Project Tree**. Observed time history data will appear in **Sources** together with summary cases. How to use the Plot Editor is covered in [Summary Plot Editor]({{site.baseurl}}/docs/summaryploteditor). Observed time history data points are plotted without lines by default.
|
||||
@ -8,13 +8,13 @@ published: true
|
||||
ResInsight provides a flexible interface to [Octave](http://www.gnu.org/software/octave/ "Octave") including:
|
||||
|
||||
- Octave functions that communicates with a running ResInsight session
|
||||
- Features to simplify managment and editing of Octave scripts from ResInsight
|
||||
- Features to simplify management and editing of Octave scripts from ResInsight
|
||||
- Commands to execute scripts using Octave.
|
||||
|
||||
The Octave functions are documented in [Octave Interface Reference]({{ site.baseurl }}/docs/octaveinterfacereference).
|
||||
|
||||
<div class="note info">
|
||||
<b>Note:</b> The Octave interface does not support Geomechanical cases and flow diagnostic results.
|
||||
<b>Note:</b> The Octave interface does not support Flow diagnostics and Injection flooding results in addition to Geomechanical cases.
|
||||
</div>
|
||||
|
||||
## Octave Script Management
|
||||
@ -56,7 +56,7 @@ When an Octave script is executed, the **Process Monitor** pops up and displays
|
||||
|
||||
|
||||
|
||||
In addition to the output from the script, it prints a start and stop timestamp. The **Clear**-button deletes all the text in the monitor, and the **Stop**-button tries to kill the running Octave process.
|
||||
In addition to the output from the script, it prints a start and stop time stamp. The **Clear**-button deletes all the text in the monitor, and the **Stop**-button tries to kill the running Octave process.
|
||||
|
||||
## Octave Script Examples
|
||||
|
||||
@ -69,7 +69,7 @@ Here are some example-scripts that illustrates the use of the octave interface.
|
||||
#### Example 1
|
||||
|
||||
```matlab
|
||||
# Calculate change of oil saturation from timestep to timestep
|
||||
# Calculate change of oil saturation from time step to time step
|
||||
SOIL = riGetActiveCellProperty("SOIL");
|
||||
SOILDIFF = SOIL;
|
||||
|
||||
|
||||
@ -12,11 +12,11 @@ To identify a ResInsight case uniquely in the Octave script, an integer Id (Case
|
||||
<b>Note:</b> The Octave interface does not support Geomechanical cases and flow diagnostic results.
|
||||
</div>
|
||||
|
||||
### Single case scripts
|
||||
### Single Case Scripts
|
||||
Single case scripts do not need to address cases explicitly, but works on what ResInsight considers being the "Current Case". When the user selects several cases and executes a script on them, ResInsight loops over all cases in the selection, sets the current case and executes the script. All references to the "Current Case" from the script will then refer to the case currently being processed by ResInsight.
|
||||
The Current Case can be accessed directly using **riGetCurrentCase()**, but the more direct way is to *omit the CaseId parameter* in the functions, the Current Case is then automatically used.
|
||||
|
||||
### Multi case scripts
|
||||
### Multi Case Scripts
|
||||
Scripts can access the selection state in ResInsight, and also retrieve lists of Case Groups and cases including some meta information. This can be used if the scripts need to get values from some cases, and store the results in others, etc.
|
||||
|
||||
### Case Types
|
||||
@ -29,7 +29,7 @@ The case type (Labeled "CaseType" in the following specification) of a case is r
|
||||
|StatisticsCase | A statistics case based on many source cases in Grid Case Group |
|
||||
|SourceCase | A binary Eclipse case in a Grid Case Group |
|
||||
|
||||
### Unresolved issues
|
||||
### Unresolved Issues
|
||||
The issue around having multiple instances of ResInsight is still not addressed, but might affect the function signatures by adding a port number parameter to all of them. We will try to find ways to avoid this, but are still not certain that we will succeed.
|
||||
|
||||
## Specification
|
||||
@ -142,13 +142,13 @@ If the CaseId is not defined, ResInsight's Current Case is used.
|
||||
This function returns a two dimensional matrix: [ActiveCells][Num TimestepsRequested] containing the requested property data from the case with CaseId.
|
||||
If the case contains coarse-cells, the results are expanded onto the active cells.
|
||||
If the CaseId is not defined, ResInsight's Current Case is used.
|
||||
The RequestedTimeSteps must contain a list of indices to the requested timesteps. If not defined, all the timesteps are returned.
|
||||
The RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.
|
||||
|
||||
#### Matrix[numI][numJ][numK][numTimestepsRequested] riGetGridProperty([CaseId], GridIndex , PropertyName, [RequestedTimeSteps], [PorosityModel = "Matrix"|"Fracture"])
|
||||
This function returns a matrix of the requested property data for all the grid cells in the requested grid for each requested timestep.
|
||||
This function returns a matrix of the requested property data for all the grid cells in the requested grid for each requested time step.
|
||||
Grids are indexed from 0 (main grid) to max number of LGR's
|
||||
If the CaseId is not defined, ResInsight's Current Case is used.
|
||||
The RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the timesteps are returned.
|
||||
The RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.
|
||||
Writing Back to ResInsight
|
||||
|
||||
#### riSetActiveCellProperty( Matrix[numActiveCells][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices], [PorosityModel = "Matrix"|"Fracture"])
|
||||
@ -223,3 +223,75 @@ This function returns the status information for a specified well for each reque
|
||||
}
|
||||
|
||||
If the CaseId is not defined, ResInsight's Current Case is used.
|
||||
|
||||
#### Matrix[numSelectedCells][5] riGetSelectedCells([CaseId])
|
||||
|
||||
This function returns a two dimensional matrix containing the cell info for each selected cell in the case with `CaseId`.
|
||||
The columns contain the following information:
|
||||
|
||||
[CaseId, GridIdx, I, J, K]
|
||||
CaseId # The ID of the case the cell resides in.
|
||||
GridIdx # The index of the grid the cell resides in.
|
||||
# Main grid has index 0
|
||||
I, J, K # 1-based index of the cell in the grid.
|
||||
|
||||
|
||||
If the CaseId is not defined, ResInsight's Current Case is used.
|
||||
|
||||
|
||||
#### Matrix[numSelectedCells][numTimestepsRequested] riGetGridPropertyForSelectedCells([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = "Matrix"|"Fracture"] )
|
||||
|
||||
This function returns a two dimensional matrix: [numSelectedCells][numTimestepsRequested] containing the requested property data from the case with CaseId.
|
||||
|
||||
If the CaseId is not defined, ResInsight's Current Case is used.
|
||||
The RequestedTimeSteps must contain a list of 1-based indices to the requested time steps. If not defined, all the time steps are returned.
|
||||
|
||||
|
||||
#### Vector[PropertyInfo] riGetNNCPropertyNames([CaseId])
|
||||
|
||||
This function returns the name and type of all NNC properties in the case as a vector of structures.
|
||||
|
||||
The structure is defined as:
|
||||
|
||||
PropertyInfo {
|
||||
PropName = string # Name of the property as received from
|
||||
# the analysis tool
|
||||
PropType = string # The type of the property: "StaticNative",
|
||||
# "DynamicNative", "Generated"
|
||||
}
|
||||
|
||||
If the CaseId is not defined, ResInsight's Current Case is used.
|
||||
|
||||
|
||||
#### Matrix[numNNCConnections][2] riGetNNCConnections([CaseId])
|
||||
|
||||
This function returns a two dimensional matrix containing grid and IJK information about each NNC connection.
|
||||
Each row contains a from and to cell for the connection.
|
||||
The cells are specified in a structure defined as:
|
||||
|
||||
CellInfo = {
|
||||
GridIndex = int # Index of the grid the cell resides in.
|
||||
# Main grid has index 0.
|
||||
I, J, K = int # 1-based index address of the cell in the grid.
|
||||
}
|
||||
|
||||
#### Matrix[numConnections][numTimestepsRequested] riGetDynamicNNCValues([CaseId], PropertyName, [RequestedTimeSteps])
|
||||
|
||||
This function returns a two dimensional matrix: [Num Connections][Num Time Steps Requested] containing the value of the requested property from the case with CaseId. The order of connections is the same as the order from `riGetNNCConnections`.
|
||||
|
||||
If the CaseId is not defined, ResInsight's Current Case is used.
|
||||
The RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.
|
||||
|
||||
#### Vector[numConnections] riGetStaticNNCValues([CaseId], PropertyName)
|
||||
|
||||
This function returns a vector of values for the requested static property for each NNC connection. The order of connections is the same as the order from `riGetNNCConnections`.
|
||||
|
||||
If the CaseId is not defined, ResInsight's Current Case is used.
|
||||
|
||||
#### riSetNNCProperty(Matrix[numNNCConnections][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices])
|
||||
|
||||
Interprets the supplied matrix as a property set defined for the NNC connections in the case, and puts the data into ResInsight as a "Generated" property with the name "PropertyName".
|
||||
The "TimeStepIndices" argument is used to "label" all the steps present in the supplied data matrix and must thus be complete.
|
||||
The time step data will then be put into ResInsight at the time steps requested.
|
||||
|
||||
If the CaseId is not defined, ResInsight's Current Case is used.
|
||||
|
||||
18
docs/PasteExcelTimeData.md
Normal file
18
docs/PasteExcelTimeData.md
Normal file
@ -0,0 +1,18 @@
|
||||
---
|
||||
layout: docs
|
||||
title: Paste Excel Time History Data
|
||||
permalink: /docs/pasteexceltimedata/
|
||||
published: true
|
||||
---
|
||||
|
||||
When text have been copied to the operating system's clipboard, it will be possible to paste that text into a summary plot. Right click on a summary plot in the **Plot Main Window Project Tree** and select **Paste Excel Data to Summary Plot**. Then a paste options dialog will appear.
|
||||
|
||||
## Paste Options Dialog
|
||||
|
||||
|
||||
Most of the fields in this dialog are the same as in the [CSV/txt import options dialog]({{ site.baseurl }}/docs/importobstimehistdata#csvtxt-import-options-dialog). Please see that section for documentation on those fields. The fields specific to the paste options dialog are as follows:
|
||||
|
||||
- **Curve Prefix** -- Curve name prefix for all curves created from the pasted data.
|
||||
- **Line Style** -- Line style to use for the curves created from the pasted data.
|
||||
- **Symbol** -- Line symbol to use for each data point on the curves created from the pasted data.
|
||||
- **Symbol Skip Distance** -- Minimum distance between two adjacent symbols on the curves. If two data points on a curve is closer than the specified distance, a symbol is not drawn for one of the data points. Default value is 0, which will draw a symbol at all data points on the curves regardless of the distance between data points.
|
||||
108
docs/PltPlot.md
Normal file
108
docs/PltPlot.md
Normal file
@ -0,0 +1,108 @@
|
||||
---
|
||||
layout: docs
|
||||
title: PLT Plot
|
||||
permalink: /docs/pltplot/
|
||||
published: true
|
||||
---
|
||||
|
||||
|
||||
|
||||
A PLT (Production Log Tool) plot is a special well plot for comparing observed production (well flow rates) and simulated production. The curves are plotted as production against measured depth (MD). Simulated pressure data is retrieved directly from the grid model or from the corresponding (\*.rft) files, while observed pressure data are loaded from well log files (\*.las).
|
||||
|
||||
## Create New PLT Plot
|
||||
There are several ways to create new PLT Plots
|
||||
|
||||
**From Project Tree in the Plot Main Window**
|
||||
- Select context command **New PLT Plot** for the _PLT Plots_ node.
|
||||
|
||||
**From the Project Tree in the Main Window**
|
||||
- Select context command **New PLT Plot** for a _Well Path_ node or a _Simulation Well_ node that has an associated well path.
|
||||
|
||||
**From the 3D view**
|
||||
- Right-click a well path, or a simulation well that has an associated well path, and select **Well Plots -> New PLT Plot**.
|
||||
|
||||
## Plot Observed Data
|
||||
To be able to plot observed production data for a well, a well log file containing that data must be imported. Production data in a well log file is expected to have column names:
|
||||
|
||||
| Component | Names |
|
||||
| ------------ | ----------------------------- |
|
||||
| Oil | _QOZT_, _QOIL_, _xxxx_QOIL_ |
|
||||
| Gas | _QOZT_, _QGAS_, _xxxx_QGAS_ |
|
||||
| Water | _QGZT_, _QWAT_, _xxxx_QWAT_ |
|
||||
| Total | _QTZT_, _QTOT_, _xxxx_QTOT_ |
|
||||
|
||||
To be able to plot simulated data for a well, the trajectory for that well have to be imported. If no well trajectory is found, ResInsight will present a warning dialog to the user.
|
||||
|
||||
|
||||
|
||||
## Property Editor
|
||||
The property editor lets the user select which curves to display in the PLT plot.
|
||||
|
||||
|
||||
|
||||
### Well Name
|
||||
Select the well to display in the plot. Only observed well paths are displayed.
|
||||
|
||||
### Sources
|
||||
After a well has been selected in the Well Name field, sources for that well should appear in the sources field. The sources are placed in one of three different groups:
|
||||
- **RFT File Cases** -- Simulation cases may have associated PLT data in _\*.rft_ file(s). If the simulation case contains such files, those are imported together with the simulation case (See the keyword `WRFTPLT` in the Eclipse manual for information)
|
||||
- **Grid Cases** -- Simulation cases
|
||||
- **Observed Cases** -- Observed data imported from well log files and well path files
|
||||
|
||||
When the user selects a source, time steps for that source appears in the **Time Steps** field.
|
||||
|
||||
### Time Steps
|
||||
The **Time Steps** field contains available time steps for the selected source(s). Some combinations of selected sources may display a filtered list of time steps instead of the union of all time steps for all selected sources. The policy is as follows:
|
||||
1. **Exclusively grid cases selected**. All available time steps for the selected grid cases are displayed.
|
||||
2. **Grid case(s) and observed data case selected**. Time steps shown are:
|
||||
- The first time step from the merged time step list from all grid cases.
|
||||
- If no time steps from grid cases match the observed time step, display the two adjacent grid case time steps.
|
||||
3. **Grid case(s) and RFT File case(s) selected**. Same display logic as point 2.
|
||||
4. **All types of cases selected**. Same display logic as point 2 with the exception that RFT File case time steps are treated as grid time steps.
|
||||
|
||||
Each time step is postfixed by an indication of which source type(s) the time step is belonging to. This indication is displayed as one or more letters within square brackets. Examples: **[ O ]**, **[ R G ]**.
|
||||
- **O** -- Time step belongs to observed data
|
||||
- **R** -- Time step belongs to RFT data
|
||||
- **G** -- Time step belongs to Grid data
|
||||
|
||||
More than one letter for one single time step, means that the time step belongs to multiple case types.
|
||||
|
||||
### Curve Selection
|
||||
The curve selection group lets the user control which component(s) of the PLT data to display.
|
||||
- **Standard Volume** -- Production data at standard conditions (normal air pressure)
|
||||
- **Reservoir Volume** -- Production data at reservoir pressure (high air pressure)
|
||||
- **Oil** -- The oil production component
|
||||
- **Gas** -- The gas production component
|
||||
- **Water** -- The water production component
|
||||
- **Total** -- Total production
|
||||
|
||||
### Zonation/Formation Names
|
||||
This property editor lets the user control how formations are handled. This is what it looks like in the PLT plot context.
|
||||
|
||||
|
||||
|
||||
Please see the [full documentation]({{site.baseurl}}/docs/formations) on the formations property editor for details.
|
||||
|
||||
<div class="note">
|
||||
When the formation names property editor is used in the context of PLT plots, the fields <b>Trajectory</b> and <b>Simulation Well</b> are hidden because those values are given by the PLT plot definition.
|
||||
</div>
|
||||
|
||||
### Legend and Axis
|
||||
|
||||
|
||||
This property editor lets the user control visual properties for the legend and axis.
|
||||
- **Depth Type** -- Select depth type, _Measured Depth_ or _Pseudo Length_
|
||||
- **Depth Unit** -- Select depth unit, _Meter_ or _Feet_
|
||||
- **Show Legends** -- Toggle on/off legends in plot
|
||||
- Visible X Axis Range
|
||||
- **Auto Scale** -- Automatically set X axis range based on data values
|
||||
- **Logarithmic Scale** -- Toggle between linear and logarithmic X axis
|
||||
- **Min** -- Set X axis minimum value
|
||||
- **Max** -- Set X axis maximum value
|
||||
- Visible Depth Range
|
||||
- **Auto Scale** -- Automatically set depth axis range based on data values
|
||||
- **Min** -- Set depth axis minimum value
|
||||
- **Max** -- Set depth axis maximum value
|
||||
|
||||
### Plot
|
||||
The PLT plot displays groups of curves. A group consists of the components oil, gas and water. The curves within a group are stacked, the biggest component first.
|
||||
@ -5,7 +5,7 @@ permalink: /docs/preferences/
|
||||
published: true
|
||||
---
|
||||
|
||||
In this section the different settings that controls the default behaviour of ResInsight is described. These settings can be controlled using the **Preference** dialog available from the **Edit -> Preferences** menu.
|
||||
In this section the different settings that controls the default behavior of ResInsight is described. These settings can be controlled using the **Preference** dialog available from the **Edit -> Preferences** menu.
|
||||
|
||||
|
||||
|
||||
@ -22,29 +22,31 @@ This group of options controls visual settings that will be used when creating n
|
||||
- **Mesh Color**
|
||||
- **Mesh Color Along Faults**
|
||||
- **Well Label Color**
|
||||
- **Font Size** -- This font size is used for all labels shown in the 3D Views
|
||||
- **Default Z Scale Factor** -- Default depth scale for grid models
|
||||
- **Font Size** -- This font size is used for all labels shown in the 3D Views.
|
||||
- **Default Z Scale Factor** -- Default depth scale for grid models.
|
||||
|
||||
### 3D views
|
||||
### 3D Views
|
||||
- **Navigation mode** -- Defines how to use the mouse to interact with with the 3D model.
|
||||
- **Use shaders** -- This option controls the use of OpenGL shaders. Should be left **On**. Available only for testing purposes.
|
||||
- **Show 3D Information** -- Displays graphical resource usage as text in the 3D view.
|
||||
|
||||
### Other
|
||||
|
||||
- **SSIHUB Address** -- Optional Url to Statoil internal web service used to import well paths.
|
||||
- **Show LAS Curve Without TVD Warning** - Turn off the warning displayed when showing LAS curves in TVD mode
|
||||
- **SSIHUB Address** -- Optional URL to Statoil internal web service used to import well paths.
|
||||
- **Show LAS Curve Without TVD Warning** - Turn off the warning displayed when showing LAS curves in TVD mode.
|
||||
|
||||
## Eclipse - tab
|
||||
|
||||
|
||||
|
||||
### Behaviour When Loading Data
|
||||
### Behavior When Loading Data
|
||||
|
||||
- **Compute DEPTH Related Properties** -- If not present, compute DEPTH, DX, DY, DZ, TOP, BOTTOM when loading new cases
|
||||
- **Load and Show SOIL** -- Control if SOIL is loaded and applied to grid
|
||||
- **Compute DEPTH Related Properties** -- If not present, compute DEPTH, DX, DY, DZ, TOP, BOTTOM when loading new cases.
|
||||
- **Load and Show SOIL** -- Control if SOIL is loaded and applied to grid.
|
||||
- **Import Faults/NNCs/Advanced MSW Data** -- Disable import of data for a case to reduce case import time.
|
||||
- **Fault Include File Absolute Path Prefix** -- Prefix used on Windows if fault files use absolute UNIX paths
|
||||
- **Fault Include File Absolute Path Prefix** -- Prefix used on Windows if fault files use absolute UNIX paths.
|
||||
- **Use Result Index File** -- If enabled ResInsight will try to save a result index file when opening a new case. The file is stored in the same directory as the _`*.EGRID`_ file with filename _`<casename>.RESINSIGHT_IDX`_ If it exists, ResInsight will use this when loading the case, resulting in a significant speedup.
|
||||
- **Skip Import of Simulation Well Data** -- Disable import of simulation well data for a case to reduce case import time (opposite toggling than the other import commands).
|
||||
|
||||
## Octave - tab
|
||||
|
||||
@ -55,15 +57,8 @@ This group of options controls visual settings that will be used when creating n
|
||||
- **Octave executable location** -- Defines the binary file location for Octave. Usually without path on Linux, and including path on Windows.
|
||||
- **Show text header when executing scripts** -- Enables the default output that octave outputs when started.
|
||||
|
||||
### Script files
|
||||
### Script Files
|
||||
|
||||
- **Shared Script Folder(s)** -- Defines the search paths for octave scripts
|
||||
- **Script Editor** -- The text editor to invoke when editing scripts
|
||||
|
||||
## Summary - tab
|
||||
|
||||
|
||||
|
||||
- **Create Summary Plots When Importing Eclipse Case** -- Automatically import the summary case and display a plot if a _`*.SMSPEC`_ file exists when importing an Eclipse binary case
|
||||
- **Default Vector Selection Filter** -- Wildcard text defining the summary vector filter to be applied by default. Default string is _`F*OPT`_
|
||||
|
||||
|
||||
@ -12,10 +12,10 @@ A regression tool for QA is build into ResInsight. This tool will do the followi
|
||||
3. When snapshot images from all projects are completed, difference images based on generated and QA-approved images are computed.
|
||||
4. Based on these three sets of images, an HTML report is created and automatically displayed.
|
||||
|
||||
## Regression test files
|
||||
## Regression Test Files
|
||||
As the model size of some test files is quite large, the test data is located in a [separate repository](https://github.com/OPM/ResInsight-regression-test). In addition, some of the files are stored using [Git Large File Storage](https://git-lfs.github.com/).
|
||||
|
||||
## How to run regression tests
|
||||
## How to Run Regression Tests
|
||||
|
||||
To be able to run regression tests you need the **compare** tool from the [ImageMagic suite](http://www.imagemagick.org/script/compare.php).
|
||||
|
||||
@ -26,7 +26,9 @@ From the ResInsight Gui select : **File->Testing->Regression Test Dialog**
|
||||
|
||||
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
|
||||
To execute a subset of tests, specify folder names separated by ";" in the *Test Filter*. If the test filter is empty, all tests are executed.
|
||||
|
||||
## Creating Regression Tests
|
||||
|
||||
An example of the folder structure is shown below:
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ published: true
|
||||
|
||||
|
||||
|
||||
Each item has a set of properties that can be editied in the **Property Editor**.
|
||||
Each item has a set of properties that can be edited in the **Property Editor**.
|
||||
|
||||
Several views can be added to the same case by right-clicking the case or a view and select **New View**. You can also **Copy** and then **Paste** a view into a Case. All the settings are then copied to the new view.
|
||||
|
||||
@ -20,7 +20,9 @@ Views of Eclipse models and Geomechanical models has a lot in common, but Eclips
|
||||
|
||||
### View properties
|
||||
|
||||
Grid appearance can be controlled from the **Property Editor** when a view is selected. This includes background color and z scaling. In addition, cell visibility controls of inactive and invalid cells. 
|
||||
Grid appearance can be controlled from the **Property Editor** when a view is selected. This includes background color and z scaling. In addition, cell visibility controls of inactive and invalid cells.
|
||||
|
||||
|
||||
|
||||
Visibility of the grid box with labels displaying the coordinates for the reservoir can also be controlled using **Show Grid Box**.
|
||||
|
||||
@ -42,9 +44,9 @@ The **Animation Progress** shows which time step you are viewing.
|
||||
|
||||
|
||||
|
||||
The **Info Text** shows general info about the case, the selected results, and some statistics.
|
||||
The **Info Text** shows general info about the case, the selected results, and some statistics. **Mobile Volume Weighted Mean** is the mean of the current **Cell Property** weighted by the **Mobile pore volume**. Mobile pore volume is defined in every cell as: MULTPV _*_ PORV(1-SWCR). If MULTPV data is not present, it is ignored in the equation. The same applies to SWCR data.
|
||||
|
||||
|
||||
|
||||
|
||||
The **Histogram** shows a histogram of the complete time series of the currently loaded **Cell Result** together with:
|
||||
|
||||
|
||||
@ -14,7 +14,7 @@ The color mapping of the displayed cell result is controlled by the **Legend Def
|
||||
- **Number format** -- Defines how the numbers are formatted
|
||||
- **Colors** -- Defines the color palette
|
||||
|
||||
- **Mapping** -- This option defines how the values are mappend onto the color distribution
|
||||
- **Mapping** -- This option defines how the values are mapped onto the color distribution
|
||||
- **Discrete Linear** -- Legend divided into linear levels defined by **Number of levels**
|
||||
- **Continuous Linear** -- Continuous linear legend with tick mark count defined by **Number of levels**
|
||||
- **Continuous Logarithmic** -- Continuous logarithmic legend with tick mark count defined by **Number of levels**
|
||||
@ -25,5 +25,5 @@ The color mapping of the displayed cell result is controlled by the **Legend Def
|
||||
- **All Timesteps** -- values for all time steps are used to find min and max value of
|
||||
the result values represented by the color legend.
|
||||
(Not available for Flow Diagnostics results)
|
||||
- **Current Time Step** -- use current (one) time step to find min and max values
|
||||
- **Current Timestep** -- use current (one) time step to find min and max values
|
||||
- **User Defined Range** -- user specifies numeric values for min and max
|
||||
|
||||
@ -13,11 +13,11 @@ The selected cells will be highlighted, text information displayed in the **Resu
|
||||
Visibility of the docking widows can be controlled from the <b>Windows</b> menu.
|
||||
</div>
|
||||
|
||||
## Result Info information
|
||||
## Result Info
|
||||
|
||||
Clicking cells will display slightly different information text based on the case type as described in the following tables:
|
||||
Clicking cells will display slightly different information text based on the case type as described in the following tables.
|
||||
|
||||
### Eclipse model
|
||||
### Eclipse Model
|
||||
|
||||
Geometry | Description
|
||||
--------------|------------
|
||||
@ -26,7 +26,7 @@ Fault face | Displays the same info as for a *Reservoir cell*. In addition th
|
||||
Fault face with NNC | Displays the same info as *Fault face*, except the Non Neighbor Connections (NNC) result value is displayed instead of grid cell value. Information added in section **-- NNC details --** is geometry information of the two cells connected by the NNC.
|
||||
Formation names| Displays name of formation the cell is part of
|
||||
|
||||
### Geomechanical model
|
||||
### Geomechanical Model
|
||||
|
||||
Name | Description
|
||||
-----------------------|------------
|
||||
@ -44,7 +44,7 @@ Additional curves can be added to the plot if CTRL-key is pressed during picking
|
||||
|
||||
To clear the cell-selection, left-click outside the visible geometry.
|
||||
|
||||
### Adding the curves to a Summary plot
|
||||
### Adding the Curves to a Summary Plot
|
||||
|
||||
The time history curves of the selected cells can be added to a Summary Plot by right-clicking in the **Result Plot** or in the 3D View.
|
||||
|
||||
@ -54,3 +54,33 @@ A dialog will appear to prompt you to select an existion plot, or to create a ne
|
||||
|
||||
|
||||
|
||||
## PVT Plot
|
||||
|
||||
Show the PVT Plot window by selecting **Windows -> PVT Plot**.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
The PVT plot window shows two plots, based on PVTNUM in the selected cell. One plots *Phase Formation Volume Factor* and the other plots *Phase Viscosity*, both against pressure. The *Phase* can be either oil or gas, and can be selected in the top left corner of the window.
|
||||
|
||||
Pressure for the selected cell, at the current time step, is marked on the plot as a vertical line, and a large circle marks the scalar value of the cell (formation volume factor/viscosity). RV for the selected cell is also shown.
|
||||
|
||||
## Relative Permeability Plot
|
||||
|
||||
Show the Relative Permeability Plot window by selecting **Windows -> Relative Permeability Plot**.
|
||||
|
||||
|
||||
|
||||
The Relative Permeability Plot window shows up to six curves, based on SATNUM in the selected cell. The curves can be turned on/off in the top left corner of the window, and they are described in the following table:
|
||||
|
||||
Name | Description | Axis
|
||||
-----|---------------------------------|-----------
|
||||
KRW | Relative permeability water | KR (Left)
|
||||
KRG | Relative permeability gas | KR (Left)
|
||||
KROW | Relative permeability oil water | KR (Left)
|
||||
KROG | Relative permeability oil gas | KR (Left)
|
||||
PCOW | Capilar pressure oil water | PC (Right)
|
||||
PCOG | Capilar pressure oil gas | PC (Right)
|
||||
|
||||
Saturation of water and gas in the selected cell, at the current time step, are annotated in the plot by a blue and orange vertical line, respectively. The intersections between the lines and the relevant curves are marked with large circles.
|
||||
|
||||
88
docs/RftPlot.md
Normal file
88
docs/RftPlot.md
Normal file
@ -0,0 +1,88 @@
|
||||
---
|
||||
layout: docs
|
||||
title: RFT Plot
|
||||
permalink: /docs/rftplot/
|
||||
published: true
|
||||
---
|
||||
|
||||
|
||||
|
||||
An RFT (_Repeated Formation Tester_) plot is a special well plot for comparing observed formation pressure and simulated formation pressure. The curves are plotted as pressure against true vertical depth (TVD). Simulated pressure data is retrieved directly from the grid model or from the corresponding (\*.rft) files, while observed pressure data are loaded from well log files (\*.las).
|
||||
|
||||
|
||||
## Create New RFT Plot
|
||||
There are several ways to create new RFT Plots.
|
||||
|
||||
**From the Project Tree in the Plot Main Window**
|
||||
- Select context command **New RFT Plot** for _Well Path_ node or _RFT Plots_ node.
|
||||
|
||||
**From the Project Tree in the 3D Main Window**
|
||||
- Select context command **New RFT plot** for a simulation well.
|
||||
|
||||
**From a 3D view**
|
||||
- Right-click a simulation well select **Well Plots -> New RFT Plot**.
|
||||
|
||||
## Import Observed RFT Data
|
||||
To be able to plot observed pressure data for a well in an RFT plot, at least one well log file from that well (e.g. \*.las) have to be imported to ResInsight. This file must contain a pressure column, which must have the name _PRESSURE_ or _PRES_FORM_. If the well log file itself does not contain a TVD column (named _TVDMSL_), a well path file (See [Well Trajectories]({{site.baseurl}}/docs/wellpaths)) for the same well must also be imported to ResInsight.
|
||||
|
||||
If no TVD data for a well is found when the user tries to plot a curve, ResInsight will present a warning dialog to the user.
|
||||
|
||||
|
||||
|
||||
## Property Editor
|
||||
The property editor lets the user select which curves to display in the RFT plot.
|
||||
|
||||
|
||||
|
||||
### Well Name
|
||||
Select the well to display in the plot. Wells postfixed by _'(Well Path)'_ have an associated well trajectory loaded.
|
||||
|
||||
### Sources
|
||||
After a well has been selected in the Well Name field, the relevant sources for that well will appear in the sources field. The sources are placed in one of three different groups:
|
||||
- **RFT File Cases** -- Simulation cases may have associated formation pressure data in _\*.rft_ file(s). If the simulation case contains such files, those are imported together with the simulation case (See the keyword `WRFTPLT` in the Eclipse manual for information).
|
||||
- **Grid Cases** -- The PRESSURE property in the 3D grid.
|
||||
- **Observed Cases** -- Observed data imported from well log files.
|
||||
|
||||
When the user selects one or more sources, a selection of their time steps appears in the **Time Steps** field.
|
||||
|
||||
### Time Steps
|
||||
The **Time Steps** field contains the relevant time steps according to the source selection. Time steps are deemed to be relevant by the following rules:
|
||||
1. If a single source or sources of the same type are selected, all available time steps in those sources are shown.
|
||||
2. If sources from two or tree types are selected, the time steps are filtered:
|
||||
- The time steps matching the observed case(s) time steps.
|
||||
- If no time steps from a case match the observed time step, the two adjacent ones are shown.
|
||||
- The first time step from any grid case(s) (as initial pressure reference).
|
||||
If the Observed data isn't selected, the RFT data serves as filter reference.
|
||||
|
||||
Each time step is postfixed by an indication of which source type(s) the time step is belonging to. This indication is displayed as one or more letters within square brackets. Examples: **[ O ]**, **[ R G ]**.
|
||||
- **O** -- Time step has observed data
|
||||
- **R** -- Time step has RFT data
|
||||
- **G** -- Time step has Grid data
|
||||
|
||||
More than one letter for one single time step, means that the time steps comes from multiple case types.
|
||||
|
||||
### Zonation/Formation Names
|
||||
This property editor lets the user control the visibility of formations lines. This is what it looks like in the RFT plot context.
|
||||
|
||||
|
||||
|
||||
Formation source *Well Path* is not available for RFT plots, as this source use MD as depth type, and RFT always use TVD. Please see the [full documentation]({{site.baseurl}}/docs/formations) on the formations property editor for details about formations.
|
||||
|
||||
<div class="note">
|
||||
When the formation names property editor is used in the context of RFT plots, the fields <b>Trajectory</b> and <b>Simulation Well</b> are hidden because those values are given by the RFT plot definition.
|
||||
</div>
|
||||
|
||||
### Legend and Axis
|
||||
|
||||
|
||||
This property editor lets the user control visual properties for the legend and axis.
|
||||
- **Show Legends** -- Toggle on/off legends in plot
|
||||
- Visible X Axis Range
|
||||
- **Auto Scale** -- Automatically set X axis range based on data values
|
||||
- **Logarithmic Scale** -- Toggle between linear and logarithmic X axis
|
||||
- **Min** -- Set X axis minimum value
|
||||
- **Max** -- Set X axis maximum value
|
||||
- Visible Depth Range
|
||||
- **Auto Scale** -- Automatically set depth axis range based on data values
|
||||
- **Min** -- Set depth axis minimum value
|
||||
- **Max** -- Set depth axis maximum value
|
||||
@ -11,22 +11,24 @@ This section describes how wells defined in the simulation are displayed, and ho
|
||||
|
||||
## Commands
|
||||
|
||||
Several commands are available as context commands on a simulation well. These commads are available either by right-clicking the well in the **3D View** or in the **Project Tree**.
|
||||
Several commands are available as context commands on a simulation well. These commands are available either by right-clicking the well in the **3D View** or in the **Project Tree**.
|
||||
|
||||
- **New Well Log Extraction Curve** -- Creates a new Well Log curve based on the selected well, the current timestep and cell property.
|
||||
( See [Well Log Plots]({{ site.baseurl }}/docs/welllogsandplots) )
|
||||
- **New Intersection** -- creates a new intersection based on the selected Simulation Well.
|
||||
( See [Well Log Plots]({{ site.baseurl }}/docs/intersections) )
|
||||
- **New Well Log Extraction Curve** -- Creates a new Well Log curve based on the selected simulation well, the current time step and cell property. ( See [Well Log Plots]({{ site.baseurl }}/docs/welllogsandplots#well-log-extraction-curves) )
|
||||
- **New Well Log RFT Curve** -- Creates a new RFT curve in a well log plot based on the selected simulation well. This option is only present if the current simulation well has RFT data. ( See [Well Log Plots]({{ site.baseurl }}/docs/welllogsandplots#well-log-rft-curves) )
|
||||
- **New RFT Plot** -- See [Well Log Plots]({{ site.baseurl }}/docs/rftplot.
|
||||
- **Plot Production Rates** -- Creates a summary plot of the selected wells production rates, along with the bottom hole pressure.
|
||||
( See [Summary Plots]({{ site.baseurl }}/docs/summaryplots) )
|
||||
- **Plot Well Allocation** -- Creates or modifies the default Well Allocation Plot to show the well
|
||||
- **Plot Well Allocation** -- Creates or modifies the default Well Allocation Plot to show the well.
|
||||
allocation for the selected well. If the case has no Fluxes the well flow rates are shown instead.
|
||||
( See [ Flow Diagnostics Plots ]({{ site.baseurl }}/docs/flowdiagnosticsplots) )
|
||||
- **Show Contributing Wells** -- This command sets up a 3D View by adding filters and modifying the Cell Result based on Flow Diagnostic Calculations to show which regions and wells that contribute to the selected well by doing:
|
||||
- Add a property filter of **Time Of Flight** to/from the selected well to show only the cells that contribute to/are influenced by the well.
|
||||
- Sets the **Cell Result** to show **Tracer With Max Fraction** based on **All Injectors** or **All Producers** (the opposite of the selected well)
|
||||
- Toggles the visibility of the other Simulation wells to show only wells contributing to/influenced by the selected well.
|
||||
|
||||
- **New Fracture** -- Creates a new fracture along the simulation well. (See [Fracture instances]({{ site.baseurl }}/docs/welllogsandplots#fracture-instances))
|
||||
- **New Intersection** -- creates a new intersection based on the selected simulation well.
|
||||
( See [Well Log Plots]({{ site.baseurl }}/docs/intersections) )
|
||||
|
||||
## Overall Settings for Simulation Wells
|
||||
|
||||
The Property Panel of the **Simulation Wells** item in the **Project Tree** contains options that are applied across all the wells, while the visualization of each single well can be controlled by the options in the property panel of that particular well, and will override the overall settings in the **Simulation Wells** item.
|
||||
@ -56,10 +58,8 @@ These options controls the visibility of different aspects of the simulation wel
|
||||
|
||||
|
||||
|
||||
- **Show Well Cells** -- This option toggles whether to add the well connection cells to the set of visible
|
||||
cells. If no cell filters are active, toggling this option will conveniently hide all other cells,
|
||||
displaying only the requested well cells.
|
||||
- **Show Well Cell Fence** -- and
|
||||
- **Show Well Cells** -- This option toggles whether to add the well connection cells to the set of visible cells. If no cell filters are active, toggling this option will conveniently hide all other cells, displaying only the requested well cells.
|
||||
- **Show Well Cell Fence** -- This options toggles whether to add all cells in a given direction ( I, J or K) to the set of visible cells, which has a connecting cell within its set.
|
||||
- **Well Fence direction** -- Controls whether to add extensions of the well cells in the I, J or K direction to the set of visible cells
|
||||
|
||||
|
||||
@ -71,14 +71,14 @@ These options controls the visibility of different aspects of the simulation wel
|
||||
- **Pipe Radius Scale** -- Scaling the pipe radius by the average i,j cell size.
|
||||
- **Sphere Radius Scale** -- Scaling connection cell spheres radius by the average i,j cell size.
|
||||
|
||||
Open Simulation Wells will be drawn with a slightly larger radius than closed wells. This makes open wells easier to see when they occupy the same cells as a closed one.
|
||||
Open Simulation Wells will be drawn with a slightly larger radius than closed wells. This makes open wells easier to see when they occupy the same cells as closed ones.
|
||||
|
||||
### Colors
|
||||
|
||||
|
||||
|
||||
- **Color Pipe Connections** -- Applies a red, green, blue or gray color to the section of the pipe touching a connection cell indicating the production status of the connection. Gas injection, oil production, water injection or closed respectively.
|
||||
- **Label Color** -- Sets the well label color in the 3D view
|
||||
- **Label Color** -- Sets the well label color in the 3D view.
|
||||
- **Unique Pipe Colors** -- Pushing this apply button will apply unique colors to all the wells, overwriting the colors they had.
|
||||
- **Uniform Pipe Colors** -- Pushing the apply button will apply the displayed color to all the wells.
|
||||
|
||||
@ -93,31 +93,31 @@ Open Simulation Wells will be drawn with a slightly larger radius than closed we
|
||||
|
||||
|
||||
|
||||
- **Well Cell Transparency** -- Controls the transparency level for the well cells
|
||||
- **Well Cell Transparency** -- Controls the transparency level for the well cells.
|
||||
- **Well Head Position** -- Controls the depth position of the wellhead. Either relative to the top of the active cells in the relevant IJ-column, or relative to the highest active cell overall.
|
||||
|
||||
## Individual Simulation Well options
|
||||
|
||||
|
||||
|
||||
Each of the wells has a set of individual settings which corresponds to the setting on the global level. See the above documentation of *Overall Settings for Simulation Wells*.
|
||||
Each of the wells has a set of individual settings which corresponds to the setting on the global level. See the documentation of [Overall Settings for Simulation Wells](#overall-settings-for-simulation-wells).
|
||||
|
||||
Except for the **Size Scaling**, these options will override the corresponding setting on the global level,
|
||||
and will result in a partially checked state on the corresponding toggle in the **Simulation Wells** property panel.
|
||||
The **Size Scaling** options, however, works relative to the scaling level set on the top level.
|
||||
|
||||
## Well pipes of Multi Segment Wells
|
||||
## Well Pipes of Multi Segment Wells
|
||||
|
||||
ResInsight reads the MSW information in the result files and uses that to create a topologically correct visualization of the Multi Segment Well. Reading this information is somewhat time consuming, and can be turned off in the [ Preferences ]({{ site.baseurl }}/docs/preferences).
|
||||
|
||||
### Geometry approximation
|
||||
### Geometry Approximation
|
||||
The pipe geometry generated for MSW's are based on the topology of the well (branch/segment structure) and the position of the cells being connected. The segment lengths are used as hints to place the branch points at sensible places. Thus the pipe geometry itself is not geometrically correct, but makes the topology of the well easier to see.
|
||||
|
||||
### Dummy branches
|
||||
### Dummy Branches
|
||||
Often MSW's are modeled using a long stem without connections and a multitude of small branches; one for each connection. ResInsight offsets the the pipe within the cell to clearly show how the topology of the well is defined.
|
||||
|
||||
|
||||
|
||||
### Picking reveals Segment/Branch info
|
||||
### Picking Reveals Segment/Branch Info
|
||||
|
||||
Branch and segment info of a MSW-connected-Cell is shown in the **Result Info** window when picking a cell in the 3D View. This can be handy when relating the visualization to the input files.
|
||||
|
||||
@ -27,13 +27,13 @@ If a project contains multiple 3D Views or Plot Windows, all of them can be expo
|
||||
The files generated are stored in a folder named _`snapshots`_ within the folder where the Project File resides.
|
||||
|
||||
<div class="note">
|
||||
Snapshots of existing views can also be created and saved from the command line.
|
||||
( See <a href="{{ site.baseurl }}/docs/commandlineparameters">Command Line Arguments</a> )
|
||||
Snapshots of existing views can also be created and saved from the command line
|
||||
( See <a href="{{ site.baseurl }}/docs/commandlineparameters">Command Line Arguments</a> ).
|
||||
</div>
|
||||
|
||||
## Advanced Snapshot Export 
|
||||
|
||||
The **Advanced Snapshot Export** command is useful for exporting several images of a specified set of views while simultaneously changing some of their settings. By using this command it is easy to document all layers of a specific model, or generate images with identical setup across several different cases. It is also easy to export an image for each of the timesteps in a case, or even a combination of all these parameters.
|
||||
The **Advanced Snapshot Export** command is useful for exporting several images of a specified set of views while simultaneously changing some of their settings. By using this command it is easy to document all layers of a specific model, or generate images with identical setup across several different cases. It is also easy to export an image for each of the time steps in a case, or even a combination of all these parameters.
|
||||
|
||||
The **Advanced Snapshot Export** is available from the **File**->**Export** menu in the **3D Main Window**
|
||||
Invoking the command will display the following dialog:
|
||||
@ -46,13 +46,13 @@ To edit a row, the row must be activated by toggling it on in the **Active** col
|
||||
|
||||
Options represented by columns:
|
||||
|
||||
- **View** -- Selects the view to modify
|
||||
- **View** -- Selects the view to modify.
|
||||
- **Result Type**, **Properties** -- Defines a list of eclipse result properties to cycle through when creating snapshots. If properties from both the dynamic and static list is needed, you must create a new row.
|
||||
- **Start Time**, **End Time** -- Defines the timestep range to cycle through when creating snapshots
|
||||
- **Start Time**, **End Time** -- Defines the time step range to cycle through when creating snapshots.
|
||||
- **Range Filter Slice**, **Range Start**, **Range End** -- Defines a range filter slice that will be added to the view, and then cycled from *Range Start* to *Range End* when creating snapshots.
|
||||
- **Cases** -- Defines the cases to cycle while creating snapshots. Normaly you can not change which case a view is displaying, but this option does temporarily.
|
||||
- **Cases** -- Defines the cases to cycle while creating snapshots. Normally you can not change which case a view is displaying, but this option does temporarily.
|
||||
|
||||
The number of exported snapshots from a row can easily end up being huge, so it is wise to use some caution. The total number will be Properties * Timesteps * Range Steps * Cases.
|
||||
The number of exported snapshots from a row can easily end up being huge, so it is wise to use some caution. The total number will be Properties * Time Steps * Range Steps * Cases.
|
||||
|
||||
Rows can be deleted and created by right-clicking in the table. 5 rows are created for convenience by default.
|
||||
|
||||
|
||||
31
docs/SummaryCrossPlots.md
Normal file
31
docs/SummaryCrossPlots.md
Normal file
@ -0,0 +1,31 @@
|
||||
---
|
||||
layout: docs
|
||||
title: Summary Cross Plot
|
||||
permalink: /docs/summarycrossplots/
|
||||
published: true
|
||||
---
|
||||
|
||||
|
||||
|
||||
A Summary Cross Plot is a window displaying a graph in the main area of the **Plot Main Window**. It is very similar to an ordinary [Summary Plot]({{site.baseurl}}/docs/summaryplots), but there are some differences:
|
||||
|
||||
- Summary Cross Plot displays one vector against another vector, not one vector against time.
|
||||
- Not possible to paste Excel/CSV data to a summary cross plot.
|
||||
- Summary cross plots have no [Plot Editor]({{site.baseurl}}/docs/summaryploteditor).
|
||||
|
||||
The only way to create a new Summary Cross Plot, is to select the context command  **New Summary Cross Plot** on the **Plot Main Window -> Project Tree -> Summary Cross Plots** item.
|
||||
|
||||
## Summary Cross Plot Curves
|
||||
New Summary Cross Plot curves are created by using the context command  **New Summary Cross Plot Curve** on a summary cross plot. To be able to display a Summary Cross Plot curve, ResInsight needs two data vectors, which are selected using the **Summary Cross Plot Curve** property editor.
|
||||
|
||||
|
||||
|
||||
In this property editor, the editor group called **Summary Vector**, has been replaced by two vector selection groups **Summary Vector Y** and **Summary Vector X**, compared to an ordinary summary plot. Like the other property editor groups, the vector selection groups works the same way as in the ordinary summary plot. However, there is one exception. The **Summary Vector X** group is missing the **Axis** field. This is because the X values have one axis only, below the plot, as opposed to the Y values, which have the left and right axis. See the [detailed description]({{site.baseurl}}/docs/summaryplots#summary-curves).
|
||||
|
||||
### Cross Plotting
|
||||
Cross plotting creates a new vector from two input vectors. Each vector entry in the resulting vector consists of one vector item value from each of the two input vectors, having equal time steps. However, in most cases the two input vectors do not share the same time steps. To be able to create a resulting cross plot vector in such cases, linear interpolation between adjacent input vector items is being used.
|
||||
|
||||
When a current time step **T** in input vector **A** is not found in input vector **B**, ResInsight interpolates between the time steps before and after **T** in vector **B**. In this way, ResInsight calculates an interpolated value for time step **T** from vector **B**. The same happens when a time step in vector **B** is not found in vector **A**.
|
||||
|
||||
If either the value at the current time step or one of the values involved in interpolation are **NULL**, the resulting vector will have a **NULL** value at the current time step. This is displayed as a 'hole' in the cross plot curve.
|
||||
|
||||
96
docs/SummaryPlotEditor.md
Normal file
96
docs/SummaryPlotEditor.md
Normal file
@ -0,0 +1,96 @@
|
||||
---
|
||||
layout: docs
|
||||
title: Summary Plot Editor
|
||||
permalink: /docs/summaryploteditor/
|
||||
published: true
|
||||
---
|
||||
|
||||
|
||||
The plot editor is a separate ResInsight dialog window where the user can select which vectors to display in a summary plot. It is also possible to edit an existing plot in this editor.
|
||||
|
||||
The upper part of the editor contains editors for selecting which vectors/summaries to display in the plot. The number of fields vary from 3 to 6 depending on the **Summary Type** currently highlighted.
|
||||
|
||||
<div class="note">
|
||||
In this context <b>highlighted</b> means the marked item with a different background color, while <b>selected</b> means an item or items that have a ticked check box.
|
||||
</div>
|
||||
|
||||
## Selection Fields
|
||||
This section describes the different selection fields in the selection part of the plot editor. A complete/valid vector selection consists of a selected source, a selected summary category, a selected item in each dynamic field (if any) and a selected vector among the Summaries.
|
||||
|
||||
### Sources
|
||||
This field contains all imported cases. Select the case(s) to display in the plot.
|
||||
|
||||
### Summary Types and Item Selection Fields
|
||||
In the mid-section of the dialog, the Summary Type and the corresponding Items can be selected.
|
||||
|
||||
- **Field** -- Select Field related vectors only
|
||||
- **Aquifer** -- Select Aquifer category vectors only
|
||||
- **Network** -- Select Network category vectors only
|
||||
- **Misc** -- Select vectors in the Misc category only
|
||||
- **Region** -- Select Region related vectors only
|
||||
- **Region number** -- Select the Region number
|
||||
- **Region-Region** -- Select Region to Region related vectors only
|
||||
- **Region numbers** -- Select the Region to Region numbers
|
||||
- **Group** - Select Group related vectors only
|
||||
- **Group name** -- Select Group name
|
||||
- **Well** -- Select Well related vectors only
|
||||
- **Well name** -- Select Well name
|
||||
- **Completion** -- Select Completion related vectors only
|
||||
- **Well name** -- Select Well name
|
||||
- **I, J, K** -- Select the I, J, K values of the completion
|
||||
- **Lgr-Completion** -- Select Completion in LGR related vectors only
|
||||
- **Well name** -- Select Well name
|
||||
- **Lgr name** -- Select Lgr name
|
||||
- **I, J, K** -- Select the I, J, K values of the completion in the Lgr.
|
||||
- **Lgr-Well** -- Select Well in LGR related vectors only
|
||||
- **Well name** -- Select Well name
|
||||
- **Lgr name** -- Select Lgr name
|
||||
- **Segment** -- Select Segment related vectors only
|
||||
- **Well name** -- Select Well name
|
||||
- **Segment number** -- Select the segment number
|
||||
- **Block** -- Select I, J, K -- Block related vectors only
|
||||
- **I, J, K** -- Select the I, J, K values of the Block.
|
||||
- **Lgr-Block** -- Select I, J, K - Block in LGR related vectors only
|
||||
- **Lgr name** -- Select Lgr name
|
||||
- **I, J, K** -- Select the I, J, K values of the Block in the Lgr.
|
||||
- **Calculated** -- Select calculated vectors created by the [curve calculator]({{site.baseurl}}/docs/curvecalculator).
|
||||
- **Imported** -- Select observed data vectors [imported from file]({{site.baseurl}}/docs/importobstimehistdata) (e.g. CSV, RSM files)
|
||||
|
||||
### Summaries
|
||||
This field contains the summaries/vectors for the highlighted summary category.
|
||||
|
||||
## Preview Plot
|
||||
When a complete/valid vector exists, one or more curves will appear in the preview plot. Each curve will also have a corresponding item in the curves field in the lower left corner. Visibility for the curves may be controlled by the checkboxes. Each curve is automatically assigned a name and appearance. However the user may modify these settings in the *Curve Name Configuration* and *Curve Appearance Assignment* fields.
|
||||
|
||||
### Plot and Curve Name Configuration
|
||||
|
||||
|
||||
The checkboxes in this field control which information elements to include in the curve name. Toggling some of the checkboxes will have no effect on some curves depending on which information elements are relevant for each curve.
|
||||
|
||||
### Curve Appearance Assignment
|
||||
Curves created are assigned individual visual properties like colors and symbols in a systematic manner to make the plots easy to read. Different aspects of the vectors are assigned to different curve appearances. E.g. using symbols to distinguish cases, while using colors to distinguish quantity.
|
||||
|
||||
These assignments can be controlled using the options in the **Curve Appearance Assignment** group.
|
||||
|
||||
|
||||
|
||||
When set to **Auto**, ResInsight assigns visual properties based on the present vector categories and the number of different values in each category.
|
||||
|
||||
When disabling the **Auto** option, you can select which of the visual curve properties to use for which summary category. The summary category that currently can be used is Case, Vector, Well, Group and Region. The visual properties supported types are Color, Symbols, Line Style, Gradient and Line Thickness.
|
||||
|
||||
The **Apply** button must be clicked to apply the new settings to all curves.
|
||||
|
||||
<div class="note">
|
||||
Assignment of curve appearance are incremental, and can end up as sub optimal if adding curves in several steps.
|
||||
Press the <b>Apply</b> button to apply consistent appearance settings according to the current curve selection.
|
||||
</div>
|
||||
|
||||
### Target Plot
|
||||
|
||||
|
||||
|
||||
In the bottom of the dialog window **Target Plot** may be specified. The target plot is the summary plot that will receive the selected curves when the **OK** or **Apply** button is clicked.
|
||||
|
||||
By default the target plot is set to **(new plot)** or to the plot selected for editing when invoking the command.
|
||||
|
||||
Setting the target plot to a different plot will add the selected curves to that plot when pressing the the **OK** or **Apply** button.
|
||||
@ -6,18 +6,35 @@ published: true
|
||||
---
|
||||
|
||||
|
||||
ResInsight can create summary plots based on vectors from SUMMARY files (`*.SMSPEC`).
|
||||
A Summary Plot is a window displaying a graph in the main area of the **Plot Main Window**. It can contain Summary Curves, Grid time history curves and pasted ascii curves ( See below ).
|
||||
|
||||
A new plot can be created by using the context menu of a plot selecting  **New Summary Plot**. The [Summary Plot Editor]({{ site.baseurl }}/docs/summaryploteditor) dialog will then open.
|
||||
|
||||
## Plot Data
|
||||
|
||||
ResInsight can create summary plots based on vectors from SUMMARY files ( _`*.SMSPEC`_ ), imported Observed Time History Data, Grid Cell Time history Curve and pasted ascii curves.
|
||||
|
||||
### SUMMARY Files
|
||||
|
||||
When opening an Eclipse case in the 3D view, the associated summary file is opened automatically by default, and made available as a **Summary Case**.
|
||||
Summary files can also be imported directly using the command: **File->Import->Import Summary Case**.
|
||||
Summary files can also be imported directly using the command: **File->Import->Import Summary Case**. All cases will be available under **Summary Cases** in the **Plot Object Project Tree**.
|
||||
|
||||
When a summary case has been imported, a Summary Plot with a default **Curve Filter** is created. This default behaviour can be configured in the [ Preferences ]({{ site.baseurl }}/docs/preferences).
|
||||
A selection of cases can be grouped by right-clicking a selection of summary cases and selecting the command **Group Summary Cases**. Summary cases can also be drag-dropped between summary groups. The groups will be used when listing the cases in the [Summary Plot Editor]({{ site.baseurl }}/docs/summaryploteditor).
|
||||
|
||||
## Summary Plots
|
||||
### Observed Data
|
||||
|
||||
A Summary Plot is a window displaying a graph in the main area of the **Plot Main Window**. It can contain **Summary Curve Filters** and **Summary Curves** ( See below ).
|
||||
See [Observed Time History Data]({{ site.baseurl }}/docs/importobstimehistdata)
|
||||
|
||||
A new plot can be created by using the context menu of a plot selecting  **New Summary Plot**.
|
||||
### Grid Cell Time History Curve
|
||||
|
||||
Time history curves from a grid cell property can also be added to a Summary Plot.
|
||||
See [Result Inspection]({{ site.baseurl }}/docs/resultinspection#result-plot).
|
||||
|
||||
### Pasted Ascii Curves
|
||||
|
||||
You can copy an ascii table directly from Excel or any text source and paste it directly into a Summary Plot using the command **Paste Excel Data to Summary Plot**. See [Paste Excel Time History Data]({{ site.baseurl }}/docs/pasteexceltimedata).
|
||||
|
||||
## Plot Settings
|
||||
|
||||
|
||||
|
||||
@ -31,42 +48,49 @@ Most of the settings for the Plot itself is controlled by its sub items in the P
|
||||
|
||||
|
||||
|
||||
- **Show Title** -- Toggles whether to show the axis title
|
||||
- **Title** -- A user defined name for the axis
|
||||
- **Title Position** -- Either *Center* or *At End*
|
||||
- **Font Size** -- The font Size used for the date/times shown at the ticks of the axis
|
||||
- **Time Mode** -- Option to show the time from Simulation Start, or as real date-times.
|
||||
- **Time Unit** -- The time unit used to display **Time From Simulation Start**
|
||||
- **Max**/**Min** -- The range of the visible time in the Plot in the appropriate time unit.
|
||||
The format of dates is _`yyyy-mm-ddThh:mm:ssZ`_
|
||||
- **Axis Title**
|
||||
- **Show Title** -- Toggles whether to show the axis title
|
||||
- **Title** -- A user defined name for the axis
|
||||
- **Title Position** -- Either *Center* or *At End*
|
||||
- **Font Size** -- The font size used for the axis title
|
||||
- **Time Values**
|
||||
- **Time Mode** -- Option to show the time from Simulation Start, or as real date-times.
|
||||
- **Time Unit** -- The time unit used to display **Time From Simulation Start**
|
||||
- **Max**/**Min** -- The range of the visible time in the Plot in the appropriate time unit.
|
||||
The format of dates is _`yyyy-mm-ddThh:mm:ssZ`_
|
||||
- **Font Size** -- The font size used for the date/times shown at the ticks of the axis
|
||||
|
||||
### Y-axis properties
|
||||
### Y-axis Properties
|
||||
|
||||
|
||||
- **Axis Title**
|
||||
- **Auto Title** -- If enabled, the y-axis title is derived from the vectors associated with the axis. Long names, acronymes and unit can be used.
|
||||
- **Names** -- Use the long name of the quantities
|
||||
- **Acronymes** -- Add the shortname/acronyme of the quantities
|
||||
- **Title** -- If **Auto Title** is disabled, the plot title is set using this field.
|
||||
- **Title Layout**
|
||||
- **Title Position** -- Controls the position of the title. Center or At End.
|
||||
- **Font Size** -- Defines the font size used by the axis title.
|
||||
- **Axis Values**
|
||||
- **Logarithmic Scale** - Draw plot curves using a logarithmic scale.
|
||||
- **Number Format** -- Defines how the legend numbers are formatted.
|
||||
- **Auto** -- Legend numbers are either using a scientific or decimal notation based on the number of digits of the value
|
||||
- **Decimal** -- Legend numbers are displayed using decimal notation.
|
||||
- **Scientific** -- Legend numbers are displayed using scientific notation (ie. 1.2e+6).
|
||||
- **Number of Decimals** -- Controls the number of digits after "." (for **Decimal** or **Scientific** format options).
|
||||
- **Scale Factor** -- "Moves" the scale value away from the values along the axis and into the unit on the axis title (for **Decimal** or **Scientific** format options).
|
||||
- **Max and Min** -- Defines the visible y range.
|
||||
- **Font Size** -- The font size used for the values shown at the ticks on the axis.
|
||||
|
||||
- **Auto Title** -- If enabled, the y-axis title is derived from the vectors associated with the axis. Names and unit are used.
|
||||
- **Title** -- If **Auto Title** is disabled, the plot title is set using this field
|
||||
- **Title Position** -- Controls the position of the title. Center or At End
|
||||
- **Font Size** -- Defines the font size used by the axis title
|
||||
- **Logarithmic Scale** - Draw plot curves using a logarithmic scale
|
||||
- **Number Format** -- Defines how the legend numbers are formatted
|
||||
- **Max and Min** -- Defines the visible y range
|
||||
|
||||
#### Number Format
|
||||
|
||||
- **Auto** -- Legend numbers are either using a scientific or decimal notation based on the number of digits of the value
|
||||
- **Decimal** -- Legend numbers are displayed using decimal notation
|
||||
- **Scientific** -- Legend numbers are displayed using scientific notation (ie. 1.2e+6)
|
||||
|
||||
### Plot mouse interaction
|
||||
### Plot Mouse Interaction
|
||||
|
||||
- **Value Tracking** -- When the mouse cursor is close to a curve, the closest curve sample is highlighted and the curve sample value at this location is displayed in a tooltip.
|
||||
- **Selection** -- Left mouse button click can be used to select several of the parts in the plot, and display them in the Property Editor:
|
||||
- The closest curve
|
||||
- Each of the Plot Axes
|
||||
- The closest curve.
|
||||
- Each of the Plot Axes.
|
||||
- The Plot itself if none of the above is hit and the Plot window is activated by the mouse click.
|
||||
- **Window Zoom** -- Window zoom is available by dragging the mouse when the left mouse button is pressed. Use  **Zoom All** to restore default zoom level.
|
||||
- **Wheel Zoom** -- The mouse wheel will zoom the plot in and out towards the current mouse cursor position
|
||||
- **Wheel Zoom** -- The mouse wheel will zoom the plot in and out towards the current mouse cursor position.
|
||||
|
||||
### Accessing the Plot Data
|
||||
|
||||
@ -74,46 +98,45 @@ The command context command **Show Plot Data** will show a window containing the
|
||||
|
||||
It is also possible to save the ascii data to a file directly by using the context command **Export Plot Data to Text File** on the plot.
|
||||
|
||||
## Summary Curve Filter
|
||||
|
||||
A Summary Curve filter is a simplified way of creating and controlling many related curves at the same time. It enables efficient search options to select a sensible subset of vectors and controls the appearance and naming of the resulting curves.
|
||||
## Summary Curves
|
||||
|
||||
A new curve filter can be created by using the context menu of a plot selecting  **New Summary Curve Filter**.
|
||||
Summary curves are normally created using the **Plot Editor** see [Summary Plot Editor]({{ site.baseurl }}/docs/summaryploteditor), but can be created directly using the context menu in the **Main Plot Window Project Tree**. Right click a Summary Plot, the Summary Curves folder or an existing curve and select the command  **New Summary Curve**.
|
||||
|
||||
|
||||
|
||||
|
||||
The property panel is divided in four main groups of options:
|
||||
The property panel is divided in three main groups of options:
|
||||
|
||||
- **Cases** -- Selecting the cases to extract data from
|
||||
- **Vector Selection** -- Selecting what vectors to create curves from
|
||||
- **Appearance Settings** -- Options controlling how colors, symbols etc are assigned to the curves
|
||||
- **Curve Name Configuration** -- Control how the curves are named
|
||||
- **Summary Vector** -- Options selecting the value to plot.
|
||||
- **Appearance Settings** -- Options controlling the color, symbol etc of the curve.
|
||||
- **Curve Name Configuration** -- Controls how the curve is labeled in the legend.
|
||||
|
||||
In addition you have the following options:
|
||||
### Summary Vector
|
||||
|
||||
- **Axis** -- Controls whether the curves are to be associated with the left or right Y-Axis
|
||||
- **Auto Apply Changes** -- When toggled, the changes in the property panel is instantly reflected in the generated and controlled curves
|
||||
- **Apply** -- Applies the settings, and thus generates and updates the controlled curves
|
||||
This group of options is used to define the summary vector data that the curve will display.
|
||||
|
||||
In the following sections the option groups are described in more detail.
|
||||
- **Case** -- Selects the imported Summary or Observed Data case to use as source.
|
||||
- **Vector** -- Displays a short name/ acronyme of the selected vector.
|
||||
- **Axis** -- Controls whether the curve is to be associated with the left or right Y-Axis.
|
||||
|
||||
### Cases
|
||||
<div class="note">
|
||||
Switching the Y-Axis for several curves in one go can be done using the context command <b>Switch Plot Axis</b>.
|
||||
</div>
|
||||
|
||||
Selects the cases to be used when searching for data vectors. Several Cases can be selected at the same time and the filter will contain the union of all vectors in those cases. Curves will be created for each selected case for the selected set of vectors.
|
||||
To optional ways to select the curve data are available: The **Vector Selection Dialog** and the **Vector Selection Filter**.
|
||||
|
||||
### Vector Selection
|
||||
|
||||
This group of options is used to define the selection of summary vectors of interest. Several filtering tools are available to make this as convenient as possible.
|
||||
The first is accessed by clicking the button **Vector Selection Dialog**. This opens a dialog similar to the one used as Plot Editor. See [Summary Plot Editor]({{ site.baseurl }}/docs/summaryploteditor).
|
||||
|
||||
The **Vector Selection Filter** group of options is a different way of selecting the curve data:
|
||||
- **Search** -- This option controls the filtering mode. Several are available and controls witch search fields that are made available. The search modes are described below
|
||||
- *Options depending on Search Mode* -- Described below.
|
||||
- *list of vector names* -- This list displays the set of vectors filtered by the search options. Use this to select which of the vectors you want as curves. **Ctrl-A** selects them all.
|
||||
- **Options depending on Search Mode** -- Described below.
|
||||
- **List of vector names** -- This list displays the set of vectors filtered by the search options. Use this to select which of the vectors you want to plot.
|
||||
|
||||
In the following, all the search fields are wildcard-based text filters. An empty search string will match anything: any value or no value at all. A single _`*`_ however, will only match something: There has to be some value for that particular quantity to make the filter match.
|
||||
|
||||
The **Vector Name** field will match the name of the quantity itself, while the additional mode specific fields will match the item(s) being addressed.
|
||||
|
||||
#### Search Modes with filter fields
|
||||
#### Search Modes with Filter Fields
|
||||
|
||||
- **All** -- A wildcard search filter applied to the colon-separated string that describes the complete vector. Eg. _`"*:*, 55, *"`_ or _`"WBHP:*"`_. This mode is the default.
|
||||
- **Filter** -- The actual filter text to apply
|
||||
@ -164,46 +187,36 @@ The **Vector Name** field will match the name of the quantity itself, while the
|
||||
- **Vector name** -- Filter for Network category vector names
|
||||
- **All (Advanced)** -- This is a complete combined search mode with all the different search options available to create advanced cross item type searches.
|
||||
|
||||
### Appearance Settings
|
||||
### Curve Name
|
||||
|
||||
Curves created by a curve filter are assigned individual visual properties like colors and symbols in a systematic manner to make the plots easy to read. Different aspects of the vectors are assigned to different curve appearances. Eg. using symbols to distinguish cases, while using colors to distinguish quantity.
|
||||
|
||||
These assignments can be controlled using the options in the **Appearance Settings** group.
|
||||
|
||||
|
||||
|
||||
When set to **Auto** ResInsight assigns visual properties based on the present vector categories and the number of different values in each category.
|
||||
|
||||
When disabling the **Auto** option, you can select which of the visual curve properties to use for which vector category. The vector Category that currently can be used is Case, Vector, Well, Group and Region. The visual properties supported types are Color, Symbols, Line Style, Gradient and Line Thickness.
|
||||
|
||||
### Curve Name Configuration
|
||||
|
||||
The user can control the curve names by toggling what part of the summary vector information to use in the name.
|
||||
|
||||
#### Contribute To Legend
|
||||
|
||||
This option controls whether the curves created by the filter will be visible in the plot legend at all. In addition will Curves with an empty name also be removed from the legend.
|
||||
|
||||
## Summary Curve
|
||||
A new curve can be created by using the context menu of a plot selecting  **New Summary Curve**.
|
||||
|
||||
|
||||
|
||||
Many of the properties of a single curve is similar to the properties described for a curve filter. There are some differences, however:
|
||||
|
||||
### Appearance
|
||||
|
||||
The curve's appearance is controlled directly, and not automatically as for **Curve Filters**.
|
||||
<div class="note">
|
||||
The appearance set on a curve in a <b>Curve Filter</b> will override the settings in the <b>Curve Filter</b> until the <b>Curve Filter</b> settings are applied again. Then the local changes on the curve are overwritten.
|
||||
</div>
|
||||
|
||||
### Curve Name
|
||||
The user can control the curve name used in the plot legend by using these options.
|
||||
|
||||
- **Contribute To Legend** -- This option controls whether the curve will be visible in the plot legend at all. A curves with an empty name will also be removed from the legend.
|
||||
- **Auto Name** -- If enabled, ResInsight will create a name for the curve automatically based on the settings in this option group.
|
||||
- **Curve Name** -- If **Auto Name** is off, you can enter any name here. If empty, the curve will be removed from the legend, but still visible in the plot.
|
||||
- **Case Name, Vector name ...** etc. -- These options controls what part of the summary vector information to use in the curve auto-name.
|
||||
|
||||
## Copy and Paste
|
||||
|
||||
Copy and Paste of selections of Summary Plots, Curves, or Curve Filter is possible using the Project Tree Context menu and standard keyboard shortcuts (CTRL-C/CTRL-V).
|
||||
Copy and Paste of selections of Summary Plots and Curves, is possible using the Project Tree Context menu and standard keyboard shortcuts (CTRL-C/CTRL-V).
|
||||
|
||||
## Summary Source Stepping
|
||||
Summary Source Stepping is a function which lets the user step through multiple vectors in one click. This function is available from both the toolbar and the **Summary Curves** property editor under a **Summary Plot** item in the **Main Plot Window Project Tree**.
|
||||
|
||||
The toolbar version may look like this
|
||||
|
||||
|
||||
|
||||
and the property editor version may looks like this
|
||||
|
||||
|
||||
|
||||
In some cases some of the stepping components are hidden, depending on the set of summary curves currently visible. When ResInsight decides which stepping component to display, all visible curves in the current plot are taken into account. If, for instance, all curves display data from the same well, the well stepping component is displayed. This policy applies to the following source dimensions:
|
||||
- Cases
|
||||
- Wells
|
||||
- Well groups
|
||||
- Regions
|
||||
- Vectors/Summaries
|
||||
|
||||
When one of the **next buttons** are clicked, all curves are changed to display data for the next item for the clicked source dimension. Example: The user clicks the **next well button**. Then the well source for all curves in the current plot are changed to display data for the next well.
|
||||
|
||||
|
||||
@ -20,9 +20,7 @@ Well log plots can be created in several ways:
|
||||
2. Right-click the empty area below all the items in the **Project Tree**.
|
||||
Select **New Well Log Plot**.
|
||||
A plot is created with one **Track** and an empty **Curve**.
|
||||
3. Right-click a LAS-file channel in the **Project Tree**.
|
||||
Select **Add to New Plot**.
|
||||
A new plot with a single **Track** and a **Curve** displaying the selected LAS-file channel is created.
|
||||
3. Right-click a LAS-file channel in the **Project Tree**. Select **Add to New Plot**. A new plot with a single **Track** and a **Curve** displaying the selected LAS-file channel is created.
|
||||
|
||||
Each **Well Log Plot** can contain several *Tracks*, and each **Track** can contain several **Curves**.
|
||||
|
||||
@ -30,17 +28,17 @@ Each **Well Log Plot** can contain several *Tracks*, and each **Track** can cont
|
||||
|
||||
Tracks and Curves can be organized using drag and drop functionality in the **Project Tree**. Tracks can be moved from one plot to another, and you can alter the order in which they appear in the **Plot**. **Curves** can be moved from one **Track** to another.
|
||||
|
||||
### Measured Depth (MD), True Veritcal Depth (TVD) and Pseudo Length (PL)
|
||||
### Measured Depth (MD), True Vertical Depth (TVD) and Pseudo Length (PL)
|
||||
|
||||
All the **Tracks** in the same plot always display the same depth range, and share the *True Vertical Depth (TVD)* or *Measured Depth (MD)* setting. In the property panel of the plot, the exact depth range can be adjusted along with the depth type setting (TVD/MD).
|
||||
|
||||
**Simulation Wells** however, is using a *Pseudo Length* instead of the real *Measured Depth* when the depth type is MD, as the MD information is not available in the restart files. The *Pseudo Length* is a length along the coarsely interpolated visualization pipe, and serves only as a very coarse estimation of an MD-like depth. Pseudo length is measured from the simulation-wells first connection-cell (well head connection) to the reservoir. This is very different from MD, which would start at RKB or at sea level.
|
||||
|
||||
### Depth unit
|
||||
### Depth Unit
|
||||
|
||||
The depth unit can be set using the **Depth unit** option. Currently ResInsight supports *Meter* and *Feet*. The first curve added to a plot will set the plot unit based on the curve unit. Additional curves added to a plot will be converted to the plot unit if needed.
|
||||
|
||||
### Depth zoom and pan
|
||||
### Depth Zoom and Pan
|
||||
|
||||
The visible depth range can be panned using the mouse wheel while the mouse pointer hovers over the plot.
|
||||
Pressing and holding **CTRL** while using the mouse wheel will allow you to zoom in or out depth-wise, towards the mouse position.
|
||||
@ -53,12 +51,12 @@ It is also possible to save the ascii data to a file directly by using the conte
|
||||
|
||||
## Tracks
|
||||
|
||||
Tracks can be created by right-clicking a **Well Log Plot** and select **New Track**
|
||||
Tracks can be created by right-clicking a **Well Log Plot** and select **New Track**.
|
||||
|
||||
|
||||
|
||||
A track controls the x-axis range of the display, and can be edited from the property panel of the **Track**.
|
||||
Logarithmic display is controlled using the **Logarithmic Scale** option.
|
||||
Logarithmic display is controlled using the **Logarithmic Scale** option. It is also possible to add **Zonation** or **Formation Names** to the track. See [Formations]({{site.baseurl}}/docs/formations) for details.
|
||||
|
||||
## Curves
|
||||
|
||||
@ -67,20 +65,20 @@ There are two types of curves: *Well Log Extraction Curves* and *Well Log LAS Cu
|
||||
|
||||
Curve visual appearance is controlled in the **Appearance** section:
|
||||
|
||||
- **Color** -- Controls the color of the curve
|
||||
- **Thickness** -- Number of pixels used to draw the curve
|
||||
- **Point style** -- Defines the style used to draw the result points of the curve, select *None* to disable drawing of points
|
||||
- **Line style** -- Defines the the style used to draw the curve, select *None* to disable line drawing
|
||||
- **Color** -- Controls the color of the curve.
|
||||
- **Thickness** -- Number of pixels used to draw the curve.
|
||||
- **Point style** -- Defines the style used to draw the result points of the curve, select *None* to disable drawing of points.
|
||||
- **Line style** -- Defines the the style used to draw the curve, select *None* to disable line drawing.
|
||||
|
||||
### Well Log Extraction Curves
|
||||
|
||||
Extraction curves acts as an artificial well log curve. Instead of probing the real well, a simulation model is probed instead.
|
||||
Extraction curves acts as an artificial well log curves. Instead of probing the real well, a simulation model is probed instead.
|
||||
|
||||
The property panel for an eclipse model is shown below:
|
||||
|
||||
|
||||
|
||||
The first group of options controls all the input needed to setup the data extraction for the curve - Well Path, Case, and result value. The selection of result value is somewhat different between geomechanical cases and Eclipse cases. In addition you can select what timestep to address if the selected property is a dynamic one.
|
||||
The first group of options controls all the input needed to setup the data extraction for the curve - Well Path, Case, and result value. The selection of result value is somewhat different between geomechanical cases and Eclipse cases. In addition you can select what time step to address if the selected property is a dynamic one.
|
||||
|
||||
<div class="note">
|
||||
Placing keyboard focus in the <b>Time Step</b> drop-downbox will allow you to use the arrow keys or the mouse wheel to quickly step through the timesteps while watching the changes in the curve.
|
||||
@ -88,25 +86,29 @@ Placing keyboard focus in the <b>Time Step</b> drop-downbox will allow you to us
|
||||
|
||||
The display name of a curve is normally generated automatically. The options grouped below **Auto Name** can be used to tailor the length and content of the curve name.
|
||||
|
||||
#### Curve extraction calculation
|
||||
#### Curve Extraction Calculation
|
||||
|
||||
This section describes how the values are extracted from the grid when creating a Well log Extraction Curve.
|
||||
This section describes how the values are extracted from the grid when creating a Well Log Extraction Curve.
|
||||
|
||||
Extraction curves are calculated by finding the intersections between a well trajectory and the cell-faces in a particular grid model. Usually there are two intersections at nearly the same spot; the one leaving the previous cell, and the one entering the next one. At each intersection point the measured depth along the trajectory is interpolated from the trajectory data. The result value is retrieved from the corresponding cell in different ways depending on the nature of the underlying result.
|
||||
|
||||
For Eclipse results the cell face value is used directly. This is normally the same as the corresponding cell value, but if a **Directional combined results** is used, ( See [ Derived Results ]({{ site.baseurl }}/docs/derivedresults) ) it will be that particular face's value.
|
||||
For Eclipse results the cell face value is used directly. This is normally the same as the corresponding cell value, but if a **Directional combined results** is used ( See [ Derived Results ]({{ site.baseurl }}/docs/derivedresults) ), it will be that particular face's value.
|
||||
|
||||
Abaqus results are interpolated across the intersected cell-face from the result values associated with the nodes of that face. This is also the case for integration point results, as they are directly associated with their corresponding element node in ResInsight.
|
||||
|
||||
#### Change Data Source for several curves
|
||||
#### Change Data Source for Several Curves
|
||||
|
||||
It is possible to change either the Case or the Well Path in several Well Log Extraction curves in one go. To do this, select the curves to change, and access the context menu. Select the command **Change Data Source**. The following dialog will appear:
|
||||
It is possible to change either the Case or the Well Path in several Well Log Extraction curves in one go. To do so, select the curves to change, and access the context menu. Select the command **Change Data Source**. The following dialog will appear:
|
||||
|
||||
|
||||
|
||||
- **Case** -- Sets this case for all the curves
|
||||
- **Case** -- Sets this case for all the curves.
|
||||
- **Well Path** -- Applies this well path to all the curves. Will not affect curves using a Simulation Well.
|
||||
|
||||
### Well Log RFT Curves
|
||||
|
||||
Well Log RFT Curves shows the values in a RFT file. See [RFT Plot]({{ site.baseurl }}/docs/rftplot) for details abuot RFT. A curve in a RFT plot will look identical to a RFT curve in a well log plot, if the depth type of the well log plot is TVD, and the interpolation type of the curve is *Point to Point*.
|
||||
|
||||
### Well Log LAS Curves
|
||||
|
||||
LAS-curves shows the values in a particular channel in a LAS-file.
|
||||
@ -124,14 +126,7 @@ You can also create a LAS-curve by a simple drag-drop operation in the <b>Projec
|
||||
ResInsight has some support for reading and writing LAS files. In the following two sections this support is described.
|
||||
|
||||
### Importing LAS-files
|
||||
LAS-files can be imported using the command: **File->Import->Import Well Logs from File**.
|
||||
|
||||
ResInsight will search for the the well name in the imported LAS-files among your existing **Well Trajectories**.
|
||||
If a match is found, the LAS-file is placed as a child of that trajectory. If not, a new empty trajectory entry is created with the imported LAS-file under it.
|
||||
|
||||
|
||||
|
||||
If the LAS-file does not contain a well name, the file name is used instead.
|
||||
See [Importing Well Log Files]({{site.baseurl}}/docs/wellpaths#importing-well-log-files) for details on LAS file import.
|
||||
|
||||
### Exporting LAS-files
|
||||
|
||||
@ -139,7 +134,7 @@ A set of curves can be exported to LAS files by right-clicking the curves, well
|
||||
|
||||
|
||||
|
||||
- **Export Folder** -- Location of the exported LAS files, one file per unique triplet of well path, case and time step
|
||||
- **Resample Curve Data** -- If enabled, all curves are resampled at the given resample interval before export
|
||||
- **Export Folder** -- Location of the exported LAS files, one file per unique triplet of well path, case and time step.
|
||||
- **Resample Curve Data** -- If enabled, all curves are resampled at the given resample interval before export.
|
||||
- **TVDRKB** -- If enabled, TVDRKB for all curves based on the listed well paths are exported. If the difference field is blank, no TVDRKB values are exported.
|
||||
|
||||
|
||||
@ -16,55 +16,54 @@ 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:
|
||||
|
||||
- Each data line must contain four numbers: X Y TVD MD separated with white-space.
|
||||
- Lines starting with "--" or "#" is considered to be comment lines
|
||||
- Lines starting with `"--" or "#"` is considered to be comment lines
|
||||
- A line starting with none-number-characters are used as a well name after the following rules:
|
||||
- If the line contains a pair of : _``` "'", "`", "´", "’" or "‘" ```_ the text between the quotation marks is used as a well name.
|
||||
- If the line contains a pair of : ``` "'", "`", "´", "’" or "‘" ``` the text between the quotation marks is used as a well name.
|
||||
- If the line contains the case insensitive string "name" with an optional ":" after then the rest of the line is used as a well name.
|
||||
- If there are no quotes or "name"'s, the complete line is used as a well name.
|
||||
- If there are several consecutive name-like lines, only the last one will be used
|
||||
- If a well name is found, a new well is created and the following data points are added to 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
|
||||
WELLNAME: WELL1
|
||||
6507.1 725 2542 2590
|
||||
6523.5 757 2549 2626.6
|
||||
6523.5 760 2559 2637.1
|
||||
-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
|
||||
550.7 1020.2 2410 2410
|
||||
551 1004.1 2422.2 2430.2
|
||||
555.2 993.9 2425 2441.6
|
||||
-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
|
||||
6507.1 725 2542 2542
|
||||
6523.5 757 2549 2578.6
|
||||
6523.5 760 2559 2589.1
|
||||
|
||||
-- A Comment new well
|
||||
This is not its name
|
||||
Name Well_2
|
||||
5507.0 4638.5 0.0 0.0
|
||||
5507 4638.5 3628.6 1628.6
|
||||
# a comment inside the data
|
||||
5297.4 4938.5 3632.4 1998.387
|
||||
550.7 1020.2 2410 2520
|
||||
551 1004.1 2422.2 2540.2
|
||||
# a comment inside the data
|
||||
555.2 993.9 2425 2551.6
|
||||
|
||||
3Q AHB-J
|
||||
5507.0 4638.5 0.0 0.0
|
||||
5507 4638.5 3628.6 1628.6
|
||||
5507 4638.5 1628.6 1628.6
|
||||
|
||||
|
||||
### Trajectory files are referenced
|
||||
### Trajectory Files are Referenced
|
||||
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.
|
||||
|
||||
<div class="note info">
|
||||
If the well trajectory file is changed and you would like a running ResInsight to update accordingly, you will need to delete all the well trajectories that emerge from that file, and import it again.
|
||||
</div>
|
||||
|
||||
## Importing from SSI-Hub (Internal Statoil web-service)
|
||||
## Importing from SSI-Hub (Internal Statoil Web-service)
|
||||
|
||||
In order to import from SSI-Hub, a project file must be present and stored to file. All imported well paths from the web service will be stored relative to this project file location. If no project file exists, the menu item is disabled.
|
||||
|
||||
@ -73,7 +72,6 @@ The command **File -> Import -> Import Well Paths From SSI-hub** launches a wiza
|
||||
<div class="note info">
|
||||
<h5>Access to web service</h5>
|
||||
The import of well paths is using a web service. If you are a Statoil employee, make sure you have access to "EDM Landmark" and "EDM Compass".
|
||||
</b>
|
||||
</div>
|
||||
|
||||
|
||||
@ -95,3 +93,42 @@ The visible wells are always shown in all the 3D Views in the complete project,
|
||||
- **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.
|
||||
|
||||
## Individual Well Trajectories
|
||||
A well trajectory (well path) will hold well log data and well path data imported from files. A well path file is placed inside the well path item, while one or more well log files are placed as child items under the well path in the project tree.
|
||||
|
||||
### Importing Well Log Files
|
||||
Well log data is usually imported from LAS-files (_\*.las_). LAS-files can be imported using the command: **File->Import->Import Well Logs from File**.
|
||||
|
||||
ResInsight will look for the the well name in the imported LAS-files among the existing **Well Paths**.
|
||||
If a match is found, the LAS-file is placed as a child of that trajectory. If not, a new empty well path entry is created with the imported LAS-file under it. A well path may have more than one LAS-files as children.
|
||||
|
||||
|
||||
|
||||
If the LAS-file does not contain a well name, the file name is used instead.
|
||||
|
||||
#### Moving LAS-file
|
||||
If ResInsight's automatic well matching fails and a LAS-file is matched with the wrong well path, it is possible to move the LAS-file to the correct well path. Select the LAS-file context menu click **Move LAS File to Well Path** and select destination well path.
|
||||
|
||||
|
||||
|
||||
### Importing Well Path Files
|
||||
See [Importing Well Paths]({{ site.baseurl }}/docs/wellpaths#ascii-well-trajectories)
|
||||
|
||||
### Look for an Existing Well Path
|
||||
Well log names may vary slightly among different files from the same well. When importing a well log file or a well log path file, ResInsight have to look for an existing well path item to ensure that the well log data and well path are imported to the correct well path item. The lookup is based on name comparison this way:
|
||||
- First remove any prefix (like `xxxxx1111/1111-` or `xxxxx1111/1111_`)
|
||||
- Then try an exact name match
|
||||
- If not found, try to match the names ignoring all spaces, dashes and underscores
|
||||
- If still no match, no existing well was found and a new one is created
|
||||
|
||||
### Well Path Property Editor
|
||||
The well path property editor lets the user control the appearance of the well path and associate the well path to a simulation well. It also gives some information about the well path metadata.
|
||||
|
||||
|
||||
|
||||
- **Appearance group** -- Settings in this group affect the well path appearance in the 3D view
|
||||
- **File group** -- Information about the well path file
|
||||
- **Simulation Well group** -- Associated simulation well. ResInsight will try to associate each well path with a simulation well. This is done in the exact same way as looking up an existing well path. If the auto-association fails, the user can set the correct simulation well here.
|
||||
- **Well Info group** -- Metadata for the well path
|
||||
- **Well Picks group** -- Information about imported [well picks]({{site.baseurl}}/docs/formations#well-picks) file containing data for the current well path
|
||||
|
||||
|
||||
47
docs/documentationTemplates.txt
Normal file
47
docs/documentationTemplates.txt
Normal file
@ -0,0 +1,47 @@
|
||||
---
|
||||
layout: docs
|
||||
title: Any Document Title
|
||||
permalink: /docs/uselowercasedocumentbasename/
|
||||
published: true
|
||||
---
|
||||
|
||||
|
||||
#### Including an image:
|
||||
|
||||
|
||||
|
||||
#### References
|
||||
|
||||
[ Result Inspection ]({{ site.baseurl }}/docs/resultinspection)
|
||||
|
||||
References to a specific heading whithin a document:
|
||||
|
||||
See [Importing Well Paths]({{ site.baseurl }}/docs/wellpaths#ascii-well-trajectories)
|
||||
|
||||
The heading lowercase with dash instead of space. No space between ](
|
||||
|
||||
#### A hint type "block" (with star)
|
||||
|
||||
<div class="note">
|
||||
<h5>Use several Project Trees and Property Editors</h5>
|
||||
If you want to pin the property editor for a certain object, you can add
|
||||
a new Project Tree and Property Editor by using the command <b>Windows->New Project and Property View</b>.
|
||||
The <code>*.rsp</code> file is an XML file, and can be edited by any text editor.
|
||||
</div>
|
||||
|
||||
#### A info type "block" (with (i) )
|
||||
<div class="note info">
|
||||
If the well trajectory file is changed and you would like a running ResInsight to update accordingly, you will need to delete all the well trajectories that emerge from that file, and import it again.
|
||||
</div>
|
||||
|
||||
#### Monospace/Code etc.
|
||||
|
||||
Monospace without the annoying box around it : _`*.GRDECL`_
|
||||
Monospace with the annoying box `*.SMSPEC`
|
||||
|
||||
##### Block of monospace:
|
||||
|
||||
WELLNAME: WELL1
|
||||
6507.1 725 2542 2590
|
||||
-999
|
||||
|
||||
@ -12,7 +12,7 @@ If you have, and would like to a use these features, please see [ Build Instruct
|
||||
### Odb Support
|
||||
ResInsight supports the elements C3D8R, C3D8 and C3D8P which are all HEX8 cells. It is also assumed that there are *no other element topologies* present in the odb file, and that there are only one part. For IJK-based range filters to work, it is also assumed that the elements in the part is topologically arranged as a complete box.
|
||||
|
||||
ResInsight loads the second frame within each odb-step, and present those as the timeseries for each result.
|
||||
ResInsight loads the second frame within each odb-step, and present those as the time series for each result.
|
||||
|
||||
All the result fields in the odb-file is then available for post processing in ResInsight, but stresses and strains are converted to pressure-positive tensors as normally used in geomechanics, instead of the normal tension-positive tensors that ABAQUS stores.
|
||||
|
||||
@ -20,7 +20,7 @@ Pressure and stress are always displayed using the *Bar* unit.
|
||||
|
||||
Other derived results are also calculated, and are described in [ Derived Results ]({{ site.baseurl }}/docs/derivedresults)
|
||||
|
||||
### ResInsight features
|
||||
### ResInsight Features
|
||||
Most of the central features of ResInsight visualization setup also applies to ABAQUS Odb models, like range filters and property filters. Well Paths will also show up along with the odb models.
|
||||
|
||||
The Octave interface, however, does not support the odb-data yet.
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 6.7 KiB After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.3 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.2 KiB After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.6 KiB After Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 8.8 KiB After Width: | Height: | Size: 9.5 KiB |
BIN
images/CompletionTypes.png
Normal file
BIN
images/CompletionTypes.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 67 KiB |
BIN
images/CompletionsIllustration.png
Normal file
BIN
images/CompletionsIllustration.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 72 KiB |
BIN
images/Completions_ExportCompletionData.png
Normal file
BIN
images/Completions_ExportCompletionData.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 44 KiB |
BIN
images/CreateCompletionOnWellPath.png
Normal file
BIN
images/CreateCompletionOnWellPath.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
BIN
images/CurveAppearanceAssignment.png
Normal file
BIN
images/CurveAppearanceAssignment.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 6.3 KiB |
BIN
images/CurveNameConfig.png
Normal file
BIN
images/CurveNameConfig.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 9.7 KiB |
BIN
images/Default.png
Normal file
BIN
images/Default.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 254 B |
Binary file not shown.
|
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 10 KiB |
BIN
images/EllipseFractureTemplateProperties.png
Normal file
BIN
images/EllipseFractureTemplateProperties.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
BIN
images/Equation_PerfInterval_K.png
Normal file
BIN
images/Equation_PerfInterval_K.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.1 KiB |
BIN
images/Equation_PerfInterval_Peaceman.png
Normal file
BIN
images/Equation_PerfInterval_Peaceman.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 5.0 KiB |
BIN
images/Equation_PerfInterval_TotalT.png
Normal file
BIN
images/Equation_PerfInterval_TotalT.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.3 KiB |
BIN
images/Equation_PerfInterval_Trans.png
Normal file
BIN
images/Equation_PerfInterval_Trans.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 2.5 KiB |
BIN
images/ExportCARFINDialog.png
Normal file
BIN
images/ExportCARFINDialog.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 36 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 15 KiB |
BIN
images/Fishbones_ExportWellSegments.png
Normal file
BIN
images/Fishbones_ExportWellSegments.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
BIN
images/Fishbones_LateralsMSWprop.png
Normal file
BIN
images/Fishbones_LateralsMSWprop.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 3.8 KiB |
BIN
images/Fishbones_PropEdit.png
Normal file
BIN
images/Fishbones_PropEdit.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
BIN
images/Fishbones_SubDefPropEdit.png
Normal file
BIN
images/Fishbones_SubDefPropEdit.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 36 KiB |
BIN
images/FlowCharacteristicsPropertyPanel.png
Normal file
BIN
images/FlowCharacteristicsPropertyPanel.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 77 KiB After Width: | Height: | Size: 83 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 24 KiB After Width: | Height: | Size: 35 KiB |
BIN
images/Folder.png
Normal file
BIN
images/Folder.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 642 B |
BIN
images/FractureInstancePropertyPanel.png
Normal file
BIN
images/FractureInstancePropertyPanel.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
BIN
images/FractureTemplates.png
Normal file
BIN
images/FractureTemplates.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
BIN
images/GridStatisticsDialog.png
Normal file
BIN
images/GridStatisticsDialog.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 28 KiB |
BIN
images/ImportObservedTimeHistoryDataDialog.png
Normal file
BIN
images/ImportObservedTimeHistoryDataDialog.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 37 KiB |
BIN
images/InfoBoxConfig.png
Normal file
BIN
images/InfoBoxConfig.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 7.5 KiB |
BIN
images/InjectionFloodingPropertyPanel.png
Normal file
BIN
images/InjectionFloodingPropertyPanel.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 6.9 KiB |
BIN
images/IntersectionAzimuthDip.png
Normal file
BIN
images/IntersectionAzimuthDip.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
BIN
images/MoveLasFileMenu.png
Normal file
BIN
images/MoveLasFileMenu.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 13 KiB |
BIN
images/NoMdWarningDialog.png
Normal file
BIN
images/NoMdWarningDialog.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 6.6 KiB |
BIN
images/NoTvdWarningDialog.png
Normal file
BIN
images/NoTvdWarningDialog.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 8.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 10 KiB |
BIN
images/PasteExcelData.png
Normal file
BIN
images/PasteExcelData.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 32 KiB |
BIN
images/PerforationIntervals_propEditor.png
Normal file
BIN
images/PerforationIntervals_propEditor.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 8.9 KiB |
BIN
images/PltLegendAndAxis.png
Normal file
BIN
images/PltLegendAndAxis.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 9.1 KiB |
BIN
images/PltPlot.png
Normal file
BIN
images/PltPlot.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 142 KiB |
BIN
images/PltPlotPropertyEditor.png
Normal file
BIN
images/PltPlotPropertyEditor.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 39 KiB After Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 9.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 100 KiB After Width: | Height: | Size: 167 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 82 KiB After Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 41 KiB After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 34 KiB After Width: | Height: | Size: 13 KiB |
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user