3D Views are the windows displaying the Grid Models. The visualization is controlled by the Project Tree item representing the View and their sub items.
+ +
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.
+ +Views of Eclipse models and Geomechanical models has a lot in common, but Eclipse views has some features that applies to Eclipse simulations only.
+ +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.
+ +
+The Cell Result item defines which Eclipse or Geomechanical property the 3D View uses for the main cell color. The property can be chosen in the property panel of the Cell Result item. The mapping between cell values and color is defined by the Legend Definition
+ along with some appearance settings on the Legend itself. (Number format etc.)
Please refer to Result Color Legend for details.
+ +
+ and Property Filters 
+In order to see different sets of cells, and cells inside the reservoir, Views use cell filters. Please refer to Cell Filters to read more about them.
+ +The Info Box controls the visibility of the animation progress, the Case description box, and the results histogram displayed in the top right corner of the view.
+ +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. 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:
+ +
The Info Box settings can be activated by clicking on the Info Text in the 3D view.
+
+
The Grids node contains child nodes for Main Grid, LGRs and Temporary LGRs where each grid’s visibilty can be controlled. The LGRs node contains all LGRs loaded from file, while Temporary LGRs contains all temporary LGRs (see Completions LGR). +Toggling Grids off will hide all grids cell geometry. This option is used to display geometry for faults and intersections. This feature is also available as a toolbutton called Hide grid cells.
+ +
+Intersections are used to cut the geometry and show result values mapped onto this geometry. +Please refer to Intersections for details.
+ +Selected overlay items in the 3D view can activate a corresponding item in the Property Editor. This is implemented for Info box and result color legends. Please note that this feature is activated by clicking inside the texture/colored part of the legend.
+ +
+
The Cell Edge Result visualization mode is one of ResInsight’s special features. Its main use is to show the MULT(X, Y, Z) properties at the same time. This will show the MULT property values different from 1.0 along the correct edges of the cells. In effect this highlights the faults and makes it easy to verify all the MULT values in one go.
+ +ResInsight supports all properties ending with X, Y, Z and X-, Y-, Z-. However, it is only the MULT property that ignores values of 1.0.
+ +When selecting a result variable for cell edge, a second legend shows up in the 3D view showing the variation in values for this second property. Color legend management is available when selecting the Legend Definition item belonging to the Cell Edge Result item.
+ +Select Custom Edge Result to specify one cell result to be mapped onto all cell edges. This way two cell results can easily be compared and visualized in the same view. The Custom Edge Result can either be a static or dynamic result.
+ +Default result mapping on faults is using the result specified in Cell Result. If a different result mapping is wanted, enable the checkbox and select the result from the result selection dialog in the Property Editor. A second legend for the fault result is added to the view.
+ +This item controls the visualization of the Eclipse simulation wells. +Please refer to Simulation Wells to read more.
+ +This item controls the visualization of well connection factors. +See Visualization and Inspection of Well Connection Factors for details.
+ +This item controls the visualization of fractures. +See Fractures for details.
+ +Visualization of the faults in the model is controlled by this item. +Please refer to Faults to read more.
+ + + + + + +ResInsight supports displaying a few types of annotations in 3D views and Contour Map view.
+ +
Global annotations may be displayed in all views and are located in the Annotations project tree node right below Grid Models (Global annotations sub tree). Local annotations are associated with a specific view and are located in the Annotations project tree node below the view node (Local annotations sub tree). All annotation types except text annotations are global only. Text annotation may be either global or local.
+ +All global annotations also have a representation in the local Annotation tree node in order to toggle visibilty per view. Those annotations are located in tree nodes starting with Global.
+ +
+Local annotations sub tree
+Global annotations sub tree
There are two ways of creating a new text annotation.
+ +
When a text annotation tree node is selected, target markers in each end of the anchor line are displayed. The targets can be clicked and dragged. Clicking the blue part lets the user drag the target vertically (along Z axis). Clicking the magenta part lets the user drag the target in the XY plane.
+ +To create a reach circle annotation, right click Annotations or Reach Circle Annotations tree node in the global annotations sub tree. Then enter values in the property editor.
+ +
To create a user defined polyline annotation, right click Annotations or User Defined Polyline Annotations tree node in the global annotations sub tree. The property editor for the newly created annotation is displayed and is in picking points mode. The user may now click on objects in the view to create polyline points. When finished, click Stop Picking Points in the property editor.
+ +
When a user defined polyline annotation tree node is selected, the polyline target markers become visible. Those can be dragged around as decribed above.
+ +To import a polyline annotation from file, right click Annotations or Polylines From File tree node in the global annotations sub tree. Then select the file to import and click OK. Imported polyline annotations are not editable.
+ +
Local annotations visibility is controlled by the check boxes in the local annotations sub tree only. Global annotations visibility, on the other hand, is controlled by the check boxes in both the global and local annotations sub trees. So in order to display a global annotation in a specific view, both the annotation tree note itself and its representation in the local sub tree must have visibilty enabled.
+ + + + + + +
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 time step between the realizations.
+ +The easiest way to create a Grid Case Group is to use the Import command: +File->Import->Eclipse Cases->Create Grid Case Group from Files or File->Import->Eclipse Cases->Create Grid Case Group from Files Recursively
+ +The latter command will display the recursive file import dialog described on the Summary Plots page.
+ +The first command will display the “old” import dialog:
+
ResInsight then creates a Grid Case Group for you, and populates its Source Cases with the Cases you selected. Then the first of those Cases are read completely, while the others are just scanned to verify that the Grids match and to detect changes in the Active Cells layout. This makes it quite fast to load even a quite large number of realizations.
+ +A Grid Case Group can be created from the right-click menu of a Result Case, Input Case or a different Grid Case Group. Source Cases can then be added by using the mouse to drag and drop cases with equal grids into the Grid Case Group’s Source Case folder. +This is useful if you want to create statistics based only on a subset of the source cases in an already created Grid Case Group.
+ +Drag and Drop of cases will normally copy the cases to the new destination, but moving them is possible by pressing and holding the Shift key while dropping.
+ +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, select New view from the right-click menu. A new 3D View will the be created on that particular case.
+ + +After creating a grid case group, an empty Statistics Case is created for you in the Derived Statistics folder of the Grid Case Group.
+ +The properties of non-calculated and calculated Statistics Case is shown below:
+ +
Three Percentile methods are implemented:
+ +When the computation is complete, you have to create a 3D View on the Statistics Case to view the results. Use the right-click menu of the Statistics Case to create it.
+ +A new statistical calculation can be created by activating the right-click menu for Derived Statistic->New Statistics Case.
+ + + + + + +
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:
+ +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.
As shown in the picture below, there are 7 different result types
+ +
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. +It is possible to select exactly what wells to investigate, and even the possible opposite flow part of the well.
+ +See also Flow Diagnostics Plots and Flow Characteristics Plot
+ +The calculations are performed by a library called opm-flowdiagnostics developed by SINTEF Digital.
+ +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. 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 SPE J., Vol. 20, No. 2, pp. 306-323, 2015. DOI: 10.2118⁄171557-PA
+ +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.
+ +There are several options available to define the particular result you want to target, as shown below:
+ +
There are two main selections you need to make: The tracers and the result property
+ +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.
+ +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 for more information.
+ +
Geomechanical results are sorted in different Result Positions:
+ +Several derived cell properties are calculated. Please refer to Derived Results for more information.
+ +This group of options controls time-lapse results to be calculated. ( See Relative Results for more information )
+ +
In the 3D view, the result property for a selected cell can be found by right-clicking on the 3D view and choosing Select Color Result. The corresponding result property will be shown in the Property Editor.
+ +
ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as Oil, Gas and Hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells.
+ +Contour Maps can be created in many different ways:
+ +
A contour Map has many of the same options available as a 3D View, but is always orthographic/parallel projection with no perspective projection or lighting available. Instead of the 3D Grid Box, the Contour Maps uses a 2D Grid simular to the 2d Intersection Views with optional Axis Lines controlled with the Show Axis Lines toggle. The name of the map can be automatically generated from the Case Name, Property Type, Aggregation Type and Sample Spacing (See Map Projection Properties for the two latter).
+ +
The Map Projection settings control how the 3D Data is aggregated onto the 2D plane. In all cases the results are calculated for a square 2D Cell lying in an arbitrary z-plane of the 3D Grid. For each 2D cell a cuboid extrusion in the full bounding extent of the 3D grid is created and this cuboid extrusion is used to calculate the volume of intersection with the 3D Grid cells for all volume weighted sums and averages. For the regular sums, a vertical ray through the center of the 2D cell is used instead. Since the ray may travel through multiple cells in the same K-layer, all the values from within one K-layer are averaged before being added to the sum.
+ +A set of parameters governs this projection:
+ +| Aggregation Type | +Description | +
|---|---|
| Oil Column | +A sum of SOIL * NTG * PORO * dZ | +
| Gas Column | +A sum of SGAS * NTG * PORO * dZ | +
| Hydrocarbon Column | +A sum of (SOIL + SGAS)* NTG * PORO * dZ | +
| Arithmetic Mean | +A volume weighted arithmetic mean of the specified cell result | +
| Harmonic Mean | +A volume weighted harmonic mean of the specified cell result | +
| Geometric Mean | +A volume weighted geometric mean of the specified cell result | +
| Volume Weighted Sum | +A volume weighted sum of the specified cell result. Suitable for volume fractions such as SOIL or PORO | +
| Sum | +A sum of the specified cell result. Suitable for absolute quantities. | +
| Top Value | +The first value encountered downwards vertically | +
| Min Value | +The minimum cell result value in the volume underneath the 2D Element | +
| Max Value | +The maximum cell result value in the volume underneath the 2D Element | +
For the Column options, no Cell Result is available in the property tree under the Contour Map.
+ +
For the Arithmetic Mean, Geometric Mean and Harmonic Mean it is also possible to specify a cell result as a weighting parameter in addition to the regular weighting by volume of intersection. The total weight will then be the volume of intersection multiplied by the specified cell result. The full range of regular cell results is available for this use.
+ + + + + + +ResInsight computes several derived results. In this section we will explain what they are, and briefly how they are calculated.
+ +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.
+ +
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.
+ +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.
+ +Cell properties with names ending in I, J, K, X, Y, or Z, and an optional “+” or “-” are combined into derived results post-fixed 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:
+ +<name>IJK cell property.
The dynamic cell property named Completion Type is calculated from the intersections between 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.
+ +If a cell is completed with multiple completions, the following priority is used : Fracture, Fishbones, and Perforation Interval.
+ +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, 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.
+ +ResInsight calculates several of the presented geomechanical results based on the native results present in the odb-files.
+ +ResInsight can calculate and display relative results, sometimes also referred to as Time Lapse results. +When enabled, every result variable is calculated as :
+ +Value’(t) = Value(t) - Value(BaseTime)
+ +Enable the Enable Relative Result option in the Relative Result Options group, and select the appropriate Base Time Step.
+ +
Each variable is then post-fixed with “_DTimeStepIndex” to distinguish them from the native variables.
+ +Note: Relative Results calculated based on Gamma values are calculated slightly differently:
+ +Gamma_Dn = ST_Dn / POR_Dn
+ +The calculated result fields are:
+ +In this text the label Sa and Ea will be used to denote the unchanged stress and strain tensor respectively from the odb file.
+ +Components with one subscript denotes the principal values 1, 2, and 3 which refers to the maximum, middle, and minimum principals respectively.
+ +Components with two subscripts however, refers to the global directions 1, 2, and 3 which corresponds to X, Y, and Z and thus also easting, northing, and depth.
+ +Two constants can be assigned to a Geomechanical case:
+ +In the following they are denoted s0 and fa respectively. Some of the derived results use these constants, that can be changed in the property panel of the Case.
+ +
Compaction is the difference in vertical displacement (U3) between a grid node and a specified reference K layer. +The reference K layer is specified in the property editor.
+ +For each node n in the grid, a node nref in the reference K layer is found by vertical intersection from the node n.
+ +If Depthn <= Depthnref:
+ +COMPACTIONn = -(U3n - U3nref)
+ +else:
+ +COMPACTIONn = -(U3nref - U3n)
+ +STii = -Saii + POR (i= 1,2,3)
+ +STij = -Saij (i,j = 1,2,3 and i not equal j)
+ +We use a value of POR=0.0 where it is not defined.
+ +STi = Principal value i of ST
+ +STM = (ST11 + ST22 + ST33)/3
+ +Q = sqrt( (3⁄2) * ( (ST1 – STM)2 + (ST2 – STM)2 + (ST3 – STM)2 ))
+ +Gammaii = STii/POR (i= 1,2,3)
+ +Gammai = STi/POR
+ +In these calculations we set Gamma to undefined if abs(POR) > 0.01 MPa.
+ +SEij = -Saij (Where POR is defined)
+ +SEij = undefined (Were POR is not defined)
+ +SEi = Principal value i of SE
+ +SEM = (SE11 + SE22 + SE33)/3
+ +SFI = ( (s0/tan(fa) + 0.5*(SE1 + SE3))sin(fa) ) /(0.5(SE1-SE3) )
+ +DSM = tan(rho)/tan(fa)
+ +where
+ +rho = 2 * (arctan (sqrt (( SE1 + a)/(SE3 + a)) ) – pi/4)
+ +a = s0/tan(fa)
+ +FOS = 1/DSM
+ +Eij = -Eaij
+ +EV = E11 + E22 + E33
+ +ED = 2*(E1-E3)/3
+ +For each face displayed, (might be an element face or an intersection/intersection box face), +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 = TS33
+ +TPH = TS31 = TSZX
+ +TPQV = TS32 = TSZY
+ +TP = sqrt(TPH2 + TPQV2)
+ +Angle of the total in-plane shear relative to the Quasi Vertical direction
+ +TPinc = acos(TPQV/TP)
+ +These are the directional angles of the face-normal itself.
+ + + + + + +
This section describes how Faults are detected and visualized. NNC’s are a part of the Faults visualization and are thus also mentioned in this section.
+ +ResInsight always scans the grids for geometrical faults when they are loaded. When two opposite cell faces of I, J, K neighbor cells does not match geometrically, they are tagged.
+ +All the tagged cell faces are then compared to the faults possibly imported from the *.DATA file in order to group them. If a particular face is not found among the fault faces defined in the *.DATA file (or their opposite faces), the cell face is added to one of two predefined faults:
The first fault is used if both the neighbor cells are active. If one or both of the neighbor cells are inactive, the second fault is used.
+ +These particular Faults will always be present, even when reading of fault information from the *.DATA file is disabled.
*.DATA-filesIf enabled in Preferences, ResInsight will import fault information from the *.DATA files and use this information to group the cell faces into named items. The imported faults are ordered in ascending order based on their name.
The DATA file is parsed for the FAULT keyword while respecting any INCLUDE and PATH keywords.
+As import of faults can be time consuming, reading of faults can be disabled from Preferences->Import faults
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.
Faults can be hidden and shown in several ways.
+ +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.
+ +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.
+ +Visualization mode and mesh lines can be controlled from the toolbar.
+ +
+Faults-Only visualization mode.
+
+ Turns faces on and mesh off
+ Turns on all faces, and shows mesh lines on faults only.
+
+ Shows labels for faultsBy clicking the
+ Faults item in the Project Tree, the following options common to all the faults are displayed:
*.DATA fileThis 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 ). 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 ).
+ +*.DATA)*.DATA file. If you need to use them, it is normally wise to set the Dynamic Face Selection to “Show Both”.*The color of the NNC faces are set to be a bit lighter than their corresponding named fault, and can not be controlled directly.
+Faults can be exported to separate files in the *grdecl file format. This is useful for example if you need a list of the geometrically detected faults that has not been covered by entries in the eclipse FAULTS keyword.
To export some faults, select the faults you want to export in the Project Tree, and select the command Export Faults … from the right-click menu.
+ +
You are then prompted to select a destination folder. Each Fault is exported to a file named Faults_<fault name>_<case name>.grdecl and stored in the selected folder.
The fault name of Undefined Grid Faults is simplified to UNDEF, while Undefined Grid Faults With Inactive is simplified to UNDEF_IA. All other faults keep their original name.
Cell Filters are used to control visibility of the cells in the 3D view. Two types of filters exists:
+ +The visibilities of cells connection to wells, and fences based on these cells can be controlled from Simulation Wells .
+(Not applicable for Geomechanical cases)
Both filter types can be turned on or off using the toggle in the Project Tree and controlled from their corresponding Property Editor.
+ +
Range Filters and Property filters can either be set to Include cells or to Exclude them.
+ +The Exclude setting is used to explicitly remove cells from the visualization, regardless of what other filters say.
+The Include setting behaves differently for Range filters and Property Filters but marks the cells as visible.
+The icon in front of the filters show a + or - sign to indicate the setting 
+
Range filters enables the user to define a set of visible regions in the 3D view based on IJK boxes. +Each Include range filter will add more cells to the visualization. The view will show the union of all the Include range filters.
+ +A new range filter can be added by activating the right-click menu for the Range Filters collection in the Project Tree.
+ + +An I,J or K-slice range filter can be added directly from a Cell in the 3D View by right-clicking the cell and using the right-click menu.
+Below is a snapshot of the Property Editor of the Range Filter :
+ +
The Start and Width labels in front of the sliders features a number in parenthesis denoting maximum available value.
+The Start labels shows the index of the start of the active cells.
+The Width labels shows the number of active cells from the start of the active cells.
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 right-click 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.
+ +The name of the property filter is automatically set to “propertyname (min .. max)” as you edit the property filter.
+ + +The context command Apply As Cell Result on a property filter, sets the Cell Color Result to the same values as the selected property filter.
+Below is a snapshot of the Property Editor of the Property Filter.
+ +
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.
+ +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 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.
+ +If the property is representing integer values, well tracer names or formation names , 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.
+ +
If it is more convenient to filter the values using a value range, toggle the Category Selection option off.
+ + + + + + +
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.
+ +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 :
+ +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.
The imported Formation Names files are then listed in the Project Tree in a folder named Formations.
+ +Formation Names files consists of a list of formation names and their k-range. Below is an example of a Formation Names file:
+ +-- Any text as comment
+'MyFormationName' 4 - 12
+'MySecondFormationName' 15 - 17
+'3 k-layer thick 18,19 and 20' 3
+'Last Name' 21 - 21
+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.
+ +
If the formation file is modified outside ResInsight, the formation data can be imported again by the right-click menu Formations->Reload. This command will import formations for the selected formation files.
+ +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.
+ +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 for details.
+ +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.
+ +Formation can be used to annotate the following plot types:
+ + + +
MANGLER BILDE
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 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.
+ +Well Pick files can be imported by using the command: File->Import->Well Data->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.
+ +See 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.
+ + + + + + +
ResInsight 3D Views has an 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.
+ +The dialog consist of three information parts.
+ +The Info Text field shows general info about the case, the selected results, and some statistics.
+ +The histogram shows a histogram of the complete time series of the currently loaded Cell Result together with:
+ +The cumulative histogram shows av accumulated version of the histogram above.
+ +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.
+ +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.
+ + +The main window also has a snapshot toolbar containing the button Snapshot All Views. This button will include a snapshot of the Grid Statistics dialog if opened.
+
This is the main window of ResInsight for all 3D related functionality and visualization. +As seen, the 3D Main Window has a central area and several docking windows surrounding it. +The different docking windows cover the following:
+ +In addition, a selected subset of actions are presented as controls in the toolbar. +The following subchapters describe the functionality and visualization pertinent to the 3D Main Window.
+ + + + + + + + +
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 piece-wise 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. These intersections can also be shown in their own separate 2D Intersection View
+ +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.
+ +All types of intersections are stored in a folder named Intersections in a View as shown below. Once created, the intersections may be copied to other views by selecting the Copy intersections to all views in case option from the right-click menu of each intersection.
+ +
Once created, the intersections may be copied to other views by selecting the Copy intersections to all views in case option from the right-click menu of each intersection.
+ +
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 intersections can be created by activating 
+ New Intersection from the right-click menu of the Intersections item in the Project Tree.
They can also be created from the right-click menu in the 3D view, as described below.
+ + +To be able to see the intersections in the 3D view, the grid cells can be hidden by disabling the Grids item in the Project Tree or activating the Hide Grid Cells toolbar button.
+The property panel of a well path based intersection is shown below:
+ +
The direction defined is used to extrude the curve in the defined direction, and thereby create a set of planes.
+ +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 the first to the second point defines the extrude direction.
+ +A new Well Path intersection can be created by right-clicking the well path in the 3D view or in the Project Tree.
+ +
When a well path intersection is created, the source well path can be changed by using the Well Path selection combo box in the Property Editor.
+ +A new Simulation Well intersection can be created by right-clicking the simulation well in the 3D view or in the Project Tree.
+ +
When a simulation well intersection is created, the source simulation well can be changed by using the Simulation Well selection combo box in the Property Editor.
+ +If the well contains more than one branch, the intersection geometry will be created for the selected branch in the Branch combo box.
+ +A new Polyline intersection can be created from the right-click 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.
+ +
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.
+ +A new Azimuth and Dip intersection can be created from the right-click 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 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:
+ +The length of the plane can also be set manually in the Property Editor.
+ +
A 2D Intersection View displays the intersection in a separate 2D view along with the defining curve. The intersection and the defining well path, simulation well or polyline is flattened to make it easier to see the intersected grid and how the well traverses it.
+ +
Each of the curve based intersections have a corresponding 2D Intersection View. Management of these views are automatic. They will be created and deleted along with the intersection.
+ +The view can be shown either by right clicking the intersection and select the command Show 2D intersection View, or by toggling the view in the project tree directly.
+ +
Scales along the edges of the view show the depth and the horizontal length of the intersection. The length is measured from the start of the wellpath or the well head of a simulation well.
+ +The view is mostly controlled by the options in the 3D view where the intersection is defined. There are, however some independent controls, like drawstyle, timestep and Z-scale.
+ +
These options are similar to the options for a regular 3D view (See View Properties )
+ +A new Intersection Box or Intersection Plane can be created from the right-click menu in the 3D view or the right-click menu in the Project Tree.
+ +
The following list describes the properties for an Intersection Box:
+ +Direct interaction in a 3D view is activated when Show 3D manipulator is pressed. Handles are displayed at the sides of the intersection object, and interactive modification is done by dragging a handle in the 3D view.
+ +
One or more views can be linked together to allow some settings like camera position and range filters, propagate from one view to another.
+ +To establish a link between views, select 
+Link Visible Views from the View toolbar. This will open a dialog where the Master View is selected. When pressing Ok in this dialog, the Linked Views items are displayed in the top of the Project Tree.
It is also possible to link specific views by selecting them and choosing Link Selected Views from the right-click menu. The following image shows the linking of a regular view with a Contour Map. Note that contour maps can never be the Master View.
+ +
When selecting a linked view in the project tree, the different options are available in the Property Editor.
+ +
A linked view can temporarily be disabled by unchecking the linked view. To disable all linked views temporarily, uncheck the top level item Linked Views.
+ +Right-clicking one of the linked view entries in the Project Tree displays the following menu entries:
+ +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:
+ +Master views have no available linking commands.
+ + + + + + +
ResInsight supports measurements in the 3D views. To enter measurement mode, press the ruler toolbar button 
+ or the keyboard shortcut Ctrl-M. This mode can also be activated from the right-click menu in a 3D view.
When ResInsight is in measurement mode, clicking on an surface in the 3D view will set the first measurement point. Clicking on a different surface will set the second measurement point, and display a label with measurements. Additional clicking will start a new measurement between two points.
+ +The measurement label contains the following:
+ +ResInsight also supports measuring a polyline (a set of line segments), which can be activated with the polyline ruler toolbar button 
+ or Ctrl-Shift-M. The measurement label will now contain additional measurements.
The measurement label contains several lengths.
+ +To leave measurement modes, press the toolbar button, press the Esc button or press the keyboard shortcut used to activate the mode again.
+ + + + + + +The color mapping of the displayed cell result is controlled by the Color Legend located below a result node in the Project Tree. The legend can be shown or hidden by checking or unchecking the box in front of the Legend Definition.
+ +
NUM or formation names.Furthermore the legend can have a semi-transparent background applied to it by selecting the *Show Box around Legends option in the Preferences dialog.
+ +
The results mapped on the 3D model can be inspected in detail by left clicking cells in the 3D view. +The selected cells will be highlighted, text information displayed in the Result Info docking window, and the time-history values plotted in the Result Plot, if available.
+ + +Visibility of the docking widows can be controlled from the Windows menu.
+Clicking cells will display slightly different information text based on the case type as described in the following tables.
+ +| Geometry | +Description | +
|---|---|
| Reservoir cell | +Displays grid cell result value, cell face, grid index and IJK coordinates for the cell. The intersection point coordinates is also displayed. Additional result details are listed in the section – Grid cell result details – | +
| Fault face | +Displays the same info as for a Reservoir cell. In addition the section – Fault result details – containing Fault Name and Fault Face information. | +
| 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 | +
| Name | +Description | +
|---|---|
| Closest result | +Closest node ID and result value | +
| Element | +Element ID and IJK coordinate for the element | +
| Intersection point | +Location of left-click intersection of the geometry | +
| Element result details | +Lists all integration point IDs and results with associated node IDs and node coordinates | +
| Formation names | +Displays name of formation the cell is part of | +
If a dynamic none-Flow Diagnostics result is active, the result values of the selected cells for all time steps are displayed in the docking window Result Plot as one curve for each cell.
+ +Additional curves can be added to the plot if CTRL-key is pressed during picking. The different cells are highlighted in different colors, and the corresponding curve is colored using the same color.
+ +To clear the cell-selection, left-click outside the visible geometry.
+ +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.
+ +
A dialog will appear to prompt you to select an existion plot, or to create a new one.
+ +
Show the PVT Plot window by selecting Windows -> PVT Plot. When it is turned on, it will only be visible when the active view is a view of an Eclipse case.
+ +
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.
+ +Show the Relative Permeability Plot window by selecting Windows -> Relative Permeability Plot. When it is turned on, it will only be visible when the active view is a view of an Eclipse case.
+ +
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.
+ +| Option | +Description | +
|---|---|
| Log Scale Kr Axis | +Enable logarithmic Kr-axis | +
| Show Unscaled | +Display curves unscaled | +
| Fixed [0, 1] X-axis | +Use a fixed range on X-axis | +
| Fixed [0, 1] Kr-axis | +Use a fixed range on Kr-axis | +
Show the Mohr’s Circle Plot window by selecting Windows -> Mohr’s Circle Plot. When it is turned on, it will only be visible when the active view is a view of an Geo Mech case.
+ +
The Mohr’s circle plot shows three circles representing the 3D state of stress for a selected cell. In addition, it shows the envelope, calculated from the cohesion and friction angle given in the geo mechanical view’s property editor. Several sets of circles and envelopes can be added by selecting more than one cell in any view (as in image above).
+ + + + + + +
Tensors are arrows showing the average principal vectors in an element, shown on every visible face of the element.
+ +The tensor results editor is found in a geo mechanical model’s View in the project tree as seen below.
+ +
The tensor arrows visualize the principal vectors in three directions. Each colored pair of arrows represents a principal. +In the example above, the orange and blue arrows represent pressures and the white arrows represent a tension.
+ +
Tensor Results of an element can be calculated from one of the three result values SE, ST and E.
+ +Choose which of the three principals to be shown. The threshold removes all principals with an absolute value less than or equal to the threshold value.
+ +Choose which color palette to use for the three arrows. The colors appear in “correct” order (first color = principal 1).
+ +The vector color Result Colors is special. By choosing this color type, a new legend will appear. This legend is defined by the values in the Legend definition of the Element Tensor Results. The extreme values of the color mapper are the extremes of the three principals combined. In the example below, the color result is SE-S1. The largest arrow (principal 1) is quite similar to the cell color, as expected.
+ +
Scale method Result scales the arrows relative to the maximum result value of all components in the model. With scale method Constant, all the arrows are set to an equal constant size. The overall arrow size can be adjusted by using the Size Scale.
+ + + + + + +
-
- 
- {{ post.author }}
-
- 
- {{ page.author }}
-
- ResInsight is an open source, cross-platform 3D visualization, curve plotting and post processing tool for Eclipse reservoir models and simulations. +It can also be configured to visualize geomechanical simulations from ABAQUS.
+ +The system also constitutes a framework for further development and can be extended to support new data sources and visualization methods, e.g. additional solvers, seismic data, CSEM, and more.
+ +The user interface is tailored for efficient interpretation of reservoir simulation data with specialized visualizations of properties, faults and wells. It enables easy handling of a large number of realizations and calculation of statistics. To be highly responsive, ResInsight exploits multi-core CPUs and GPUs. Efficient plotting of well log plots and summary vectors is available through selected plotting features.
+ +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.
+ResInsight also supports selected parts of Eclipse input files and can read grid
+information and corresponding cell property data sets from *.GRDECL files.
+Well log data can be imported from *.LAS files.
ResInsight can also be built with support for Geomechanical models from ABAQUS in the *.odb file format.
ResInsight contains several pre-processing tools for updating and improving Eclipse reservoir models, including but not limited to:
+ +Flow diagnostics calculations are embedded in the user interface and allows instant visualization of several well-based flow diagnostics properties, such as : Time of flight, flooding and drainage regions, well pair communication, well tracer fractions, well allocation plots and well communication lines. The calculations are performed by a library called opm-flowdiagnostics developed by SINTEF Digital. More…
+ +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.
+ +ResInsight is developed by Ceetron Solutions in collaboration with with Equinor.
+ +ResInsight is a part of the Open Porous Media Initiative. +The software is hosted at GitHub, and the development progress can be monitored there. The GitHub issue tracker is heavily used to organize the development process.
+ +The software is licensed under GPL 3+, see Licensing details.
+ +
--replaceSourceCases *.dev* files.
-*.rsp file is an XML file, and can be edited by any text editor.
-octave.exe will not work as it is launching the octave GUI.
-*.rsp file is an XML file, and can be edited by any text editor.
-The completions defined in ResInsight can be exported to Eclipse for use in new simulation runs. The commands Export Completion Data For Visible Wells, Export Completion Data For Visible Simulation Wells and Export Completion Data For Selected Wells can be used to invoke the export. The commands are available by right clicking Well Paths or Simulation Wells in the Project Tree. The first command is available from the File->Import menu as well.
+ +
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 (Ky) and PERMZ (Kz):
+ +
The Peacman radius (pressure equivalent radius) for the cell is then calculated, using permeabilities and cell sizes (Dy and Dz):
+ +
The x-component of the transmissibility vector is calculated, using the length of the perforation in the x direction (lx), the well radius (rw) 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), this value is exported in the COMPDAT/COMPDATL keywords 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/COMPDATL keywords (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.
+ +For cases with high differential depletion, it is possible to scale the transmissibilities from the grid cells into the well (via the fracture) by the well drawdown. This enables the simulation to take into account that the flow will take different paths into the well as the pressure differential between the surrounding grid cells increases. If enabled, a time step for the grid pressures have to be selected. The list of time steps will also show the time step in which the wells first show a Well Bore Hole Pressure (WBHP) larger than zero in the Summary Case information.
+ +
Having chosen a time step for differential depletion scaling a source for the well pressures can be chosen. If WBHP From Summary Case is picked, the WBHP value in the summary case for the chosen time step is used. However, if the chosen time step precedes the production start of a well, the value set in WBHP Before Production Start is used.
+ +
If, however, a Fixed User Defined WBHP is chosen, the provided WBHP value is used for all wells.
+ +
At the top of the exported transmissibilities for fractures, a fracture report summary is displayed. This section displays the different properties for the fractures used to compute the transmissibility values.
+ +One of the tables displays derived data, see the example here:
+ + Tr #con Fcd Area KfWf Kf Wf Xf H Km
+[cP.rm3/day/bars] [] [m2] [mDm] [mD] [m] [m] [m] [mD]
+----------------------------------------------------------------------------------------------------
+ 110.834 24 276.168 9315.748 54.889 3805.029 0.014 61.628 75.580 13.778
+In addition to scaling the transmissibilities in the fracture output, using pressure differential depletion scaling will also provide a table with information regarding the scaling performed for each well. This table will show the well name, fracture name and the source of the Well Bore Hole Pressure (WBHP From Summary Case or Fixed User Defined WBHP). For WBHP From Summary Case the User WBHP column will describe the well pressure used for all time steps before the production starts according to the summary case information and the Actual WBHP will describe the well pressure used in the scaling, which will be different from the User WBHP if the scaling is performed for a time step following the well productions start. Finally the columns Min Pressure Drop and Max Pressure Drop describes the minimum and maximum well drawdown for this particular fracture.
+ +--
+-- Pressure Depletion Time step: 01.Feb 2001
+-- WBHP Source: WBHP From Summary Case
+-- User Defined WBHP: 200
+-- Well Fracture Actual WBHP Min Pressure Drop Max Pressure Drop
+------------------------------------------------------------------------------
+-- B-1H Fracture_01 221.68147 0.04077 45.10402
+-- B-1H Fracture_02 221.68147 0.00624 36.02608
+-- B-4DH Fracture_07 200.00000 28.21733 97.34970
+--
+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.
+ +WELSPECS
+-- Well Grp I J RefDepth WellType
+ Well Path B GR 26 45 1230 Oil \
+\
+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.
+ +WELSPEC
+-- Well Grp I J RefDepth WellType
+ Well Path B GR 26 45 1230 Oil \
+\
+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 /
+/
+Completion data for LGR grids are exported to a separate file having the same name as the main grid completions file postfixed by “_LGR”. Instead of using the WELSPECS and COMPDAT keywords, the WELSPECL and COMPDATL keywords are used. Those tables are simlar to the WELSPECS and COMPDAT tables, except from including the columns LGR and LgrName, respectively. The extra columns contains the name of the LGR grid.
+ +WELSPECL
+-- Well Grp LGR I J RefDepth WellType
+ UWell-1 1* WELLI1 2 9 1* OIL /
+ /
+COMPDATL
+-- Well LgrName I J K1 K2 Status SAT TR DIAM KH S Df DIR
+-- ---- Completions for completion type Perforation ----
+-- Perforation Completion : MD In: 63.6509 - MD Out: 67.0264 Transmissibility: 6.10676
+ UWell-1 WELLI1 2 9 6 6 OPEN 1* 6.106763E+00 0.21600 1* 0.00000 1* 'Y' /
+-- Perforation Completion : MD In: 67.0264 - MD Out: 70.402 Transmissibility: 6.10679
+ UWell-1 WELLI1 2 8 6 6 OPEN 1* 6.106791E+00 0.21600 1* 0.00000 1* 'Y' /
+The previous section describes the export of COMPDATL for completions intersecting existing LGRs, loaded from file. This section will describe how to have ResInsight create temporary LGRs around completions, and then export COMPDATL for those LGRs. +To accomplish this, do the following:
+ +In addition to the completion data, the geometrical definition of all temporary LGRs is also exported into “*.dat” files.
+It is possible to export all the completions to a text file containing the Eclipse input data +keywords needed to represent the completions as a Multi Segment Well. This is done by checking the Include Multi Segment Well Model. All completions are supported and are exported in somewhat different ways.
+ +In the output file there are data for three Eclipse keyword specified.
+ +WELSEGS defines multi-segment wells. 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:
+ +The following WELSEGS entries contains information about each segment:
+ +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 containing the following field:
+ +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
+ +Fractures and Perforations may also be exported as Multi-Segment Wells. In the case of Fractures, ResInsight will create one segment for the entire fracture, with a number of COMPSEGS-entries corresponding to the cells intersecting the fracture. In this case, the Diam and Rough parameters are not used for anything and the length of the fracture segment is nominal. An example of a Fracture entry is shown below.
+ +WELSEGS
+-- Name Dep 1 Tlen 1 Vol 1 Len&Dep PresDrop
+ C-1 H 2575.39553 2919.53029 1* INC H-- /
+-- First Seg Last Seg Branch Num Outlet Seg Length Depth Change Diam Rough
+-- Fracture Segments
+-- Diam: MSW - Default Dummy
+-- Rough: MSW - Default Dummy
+-- Traversal Fracture 02 connected to Main stem segment 11
+ 25 25 2 11 0.01000 0.00000 0.15000 0.00005 /
+ /
+COMPSEGS
+-- Fractures
+-- Name
+ C-1 H /
+-- I J K Branch no Start Length End Length Dir Pen End Range Connection Depth
+ 27 43 1 2 11.27214 11.28214 /
+ 26 44 1 2 11.27214 11.28214 /
+The entries for Perforations are simpler. No additional branches are created as the perforation intervals are all on the main bore and all perforated cells are listed as COMPSEG entries very similar to normal COMPDAT export of perforation intervals.
+ +WELSEGS
+-- Name Dep 1 Tlen 1 Vol 1 Len&Dep PresDrop
+ B-1 AH 2530.38706 3137.28258 1* INC H-- /
+-- First Seg Last Seg Branch Num Outlet Seg Length Depth Change Diam Rough
+-- Main Stem Segments
+ 2 2 1 1 16.33624 6.96924 0.15200 0.00001 /
+ 3 3 1 2 11.77390 4.75668 0.15200 0.00001 /
+ 4 4 1 3 9.49721 3.63598 0.15200 0.00001 /
+ 5 5 1 4 6.77104 2.59228 0.15200 0.00001 /
+ 6 6 1 5 29.44930 10.10431 0.15200 0.00001 /
+ 7 7 1 6 27.93603 7.96718 0.15200 0.00001 /
+ 8 8 1 7 13.95369 3.66086 0.15200 0.00001 /
+ /
+COMPSEGS
+-- Name
+ B-1 AH /
+-- I J K Branch no Start Length End Length Dir Pen End Range Connection Depth
+ 10 24 1 1 3137.28258 3153.61882 /
+ 10 24 2 1 3153.61882 3165.39273 /
+ 9 24 2 1 3165.39273 3174.88994 /
+ 9 25 2 1 3174.88994 3181.66098 /
+ 9 25 3 1 3181.66098 3211.11028 /
+ 9 25 5 1 3239.04631 3253.00000 /
+ /
+Eclipse Properties can be exported to Eclipse ASCII files. +This is particularly useful when a new property is generated using Octave. +The generated property can be exported for further use in the simulator.
+ +To export the property currently active in the 3D View, activate the right-click menu on a Cell Result item in the Project Tree.
+ +
The following dialog will appear:
+ +
The exported file has the following format, that matches the Eclipse input format:
+ +-- Exported from ResInsight
+<keyword>
+<One number per cell separated by spaces>
+/
+In order to export well paths to dev files, select the menu item File -> Export -> Export Visible Well Paths or select one or more well paths and then select one of the items in the context sub menu Export Well Paths.
+ +A dialog appears after selecting an export well path command.
+ +
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:
+ +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.
+ +
ResInsight features the following capabilities for export of data to reporting or further analysis:
+ +The following subchapters details the functionality and capabilites.
+ + + + + + + + +Sub-sections of the Eclipse Grid with Parameters and Faults can be exported to Eclipse ASCII files in order to create new +Simulations on the sub-section.
+ +To launch the export dialog, right-click on either the 3D-view in question or the Cell Result.
+ +
The Export dialog will allow the user to export grid data as ascii (An Eclipse Input Grid) to a specific file name by checking the Export Grid Data option. +If the option Export in Local Coordinates is checked, the UTM-portion of the coordinates will be stripped and the Grid will +be exported in a local coordinate system with no reference to actual location.
+ +The Grid Box selection group will allow the user to choose whether to export an IJK bounding box surrounding:
+ +Furthermore, by checking Make Invisible Cells Inactive any cells that are within the IJK bounding box, but are invisible, will be made +inactive (ACTNUM = 0) in the exported grid.
+ +The grid can be refined by a different integer in all three directions by changing the default value of Cell Count = 1 for I, J or K. The grid results will be not be interpolated but all new cells will inherit the value of their original cell.
+ +Optionally export fault data to a separate fault file or append to the existing grid. Also, fault data can be ommitted by choosing “Do not Export” from the +Export Fault Data drop down list.
+ +
The Static result values in the Grid may be exported as Eclipse Input Parameters. The default parameters are +EQLNUM, FIPNUM, NTG, PERMX, PERMY, PERMZ, PORO, PVTNUM, SATNUM and SWATINIT. ACTNUM is exported by default in the Grid Export file.
+ +Other statuc result variables may be selected.
+ +By default the Parameters will be exported to a separate file per parameter in the grid folder location. However it is possible to +append them to the grid file, export them all into a single parameter file or omit them completely be selecting different options in the Export Parameters drop down list.
+ + + + + + +ResInsight has several commands to create snapshots conveniently. 3 commands to take snapshots of existing Plot and 3D Views directly, and a more advanced export command that can automatically modify Eclipse 3D Views before snapshotting them.
+ +The commands to snapshot existing views and plots are available from the toolbar and the Edit and File->Export menus in the main windows 
+
+A snapshot of the active view is copied to the clipboard using Edit -> Copy Snapshot To Clipboard.
+ +
+Image export of the currently active 3D View or Plot Window can be launched from File -> Export -> Snapshot To File.
+ +
+If a project contains multiple 3D Views or Plot Windows, all of them can be exported in one go using File -> Export -> Snapshot All Views To File. This will either export all the 3D Views or all the Plot Windows, depending on whether you invoke the command in the 3D Main Window or the Plot Main Window.
+ +The files generated are stored in a folder named snapshots within the folder where the Project File resides.
Snapshots of existing views can also be created and saved from the command line + ( See Command Line Interface ).
+
+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:
+ +
This table defines which 3D Views to modify, and how to modify them. Each row defines the modifications of a specific view, and for all the combinations a row specifies, a snapshot is generated.
+ +To edit a row, the row must be activated by toggling it on in the Active column, then double click on the cell to edit.
+ +Options represented by columns:
+ +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.
+ +The snapshots will be generated and saved to the folder displayed in the Export Folder field, when pressing the Export button. This might take quite some time, depending on you settings.
+ + + + + + +The source code is hosted at GitHub
+ +In a git enabled shell do: git clone https://github.com/OPM/ResInsight.git
Visual Studio 2015 and later is supported.
+ +GCC version 4.9 or later is supported. On RedHat Linux 6 you need to install devtoolset-3, and enable it with
+ +source /opt/rh/devtoolset-3/enable
+Qt Qt5 version 5.6.0 or later is supported.
+ +On some configurations you will be asked to specify the location of Qt5. Example for Windows :
+Qt5_DIR=d:\Qt\5.11.3\msvc2017_64\lib\cmake\Qt5
Qt4 is marked as deprecated and support for using Qt4 will soon be removed.
+Qt Qt4 version 4.6.2 or later is supported. On Windows we recommend Qt-4.8.7, while the default installation will do under Linux.
+ +RESINSIGHT_BUILD_WITH_QT5=FALSE
You will need to patch the Qt sources in order to make them build using Visual Studio 2015 using this : +Qt-patch
+ +CMake version 2.8 or later is supported.
+ +The ResInsight build may be configured in different ways, with optional support for Octave plugins, +ABAQUS ODB API, HDF5, Pyton, 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.
+ +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.
+ +Typical usage is to follow the build instructions above to build the makefiles. Then go to the build directory, and run:
+ +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.
+ +| CMake Name | +Default | +Description | +
|---|---|---|
RESINSIGHT_BUILD_DOCUMENTATION |
+OFF | +Use Doxygen to create the HTML based API documentation. Doxygen must be properly installed. | +
RESINSIGHT_ENABLE_GRPC |
+OFF | +Enable gRPC scripting server. Required to be able to use ResInsight from Python | +
RESINSIGHT_HDF5_DIR |
+Blank | +Windows Only: Optional path to HDF5 libraries on Windows | +
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 | +
To be able to modify Advanced Options from the CMake User Interface, tick the checkbox Advanced
+ +| CMake Name | +Default | +Description | +
|---|---|---|
RESINSIGHT_BUILD_WITH_QT5 |
+ON | +If ON, use Qt5. If OFF, use Qt4 (Support for Qt4 is deprecated and will be removed) | +
RESINSIGHT_QT5_BUNDLE_LIBRARIES |
+OFF | +Linux only: Include Qt5 libraries in the installation package | +
RESINSIGHT_BUNDLE_OPENSSL |
+OFF | +Bundle the OpenSSL library DLLs in the Windows installer package | +
RESINSIGHT_ENABLE_COTIRE |
+OFF | +Experimental speedup of compilation using cotire | +
RESINSIGHT_ENABLE_PROTOTYPE_FEATURE_SOURING |
+ON | +Enable Souring features | +
RESINSIGHT_INCLUDE_APPFWK_TESTS |
+OFF | +Include unit tests from thirdparty libraries AppFwk and VizFwk | +
RESINSIGHT_INCLUDE_APPLICATION_UNIT_TESTS |
+OFF | +Include Application Code Unit Tests | +
RESINSIGHT_PRIVATE_INSTALL |
+ON | +Linux only: Include libecl libraries in the installation package | +
RESINSIGHT_HDF5_BUNDLE_LIBRARIES |
+OFF | +Linux only: Include HDF5 libraries in the installation package | +
These parameters are considered beta, and might change.
+ +| CMake Name | +Default | +Description | +
|---|---|---|
RESINSIGHT_ENABLE_GRPC |
+OFF | +Enable gRPC scripting server. Required to be able to use ResInsight from Python | +
RESINSIGHT_GRPC_PYTHON_EXECUTABLE |
+Blank | +Location of Python3 executable | +
RESINSIGHT_GRPC_INSTALL_PREFIX |
+Blank | +Linux only : Installation prefix for gRPC | +
Scripting of ResInsight is possible from a Python library. The build configuration is a bit involved and is under review.
+ +The current build instructions are specified in text files in the ResInsight repository.
+ + + +See Python API for how to use the Python library.
+ +Octave is now detected searching the file system. If Octave is not detected, the following file path variable must be defined:
+ +OCTAVE_CONFIG_EXECUTABLE : d:\octave\Octave-4.0.0\bin\octave-config.exe
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.
+ +The following command line can be used as a starting point to install required libraries
+sudo apt-get install git cmake build-essential octave liboctave-dev qtbase5-dev qtscript5-dev
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.
+ +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.
+ +Use an advanced flag RESINSIGHT_HDF5_BUNDLE_LIBRARIES to include HDF5 libraries in the installation package.
+ +Tested with 1.8.18 on windows, and default installation on RedHat 6.
+ + + + + + +See the following for common install procedures and options:
+ + + +See Build Instructions for the complete list of configuration options including support for +Octave plugins, ABAQUS ODB API, and HDF5.
+ +ResInsight is under continuous development targeting two major releases per year. +For an overview of some of its new and exciting features, see the following:
+ +Sign up to be notified of new releases
+ +For the complete list of releases and updates, please visit ResInsight on Github.
+ + + + + + + + +Please not that the distribution by the OPM Project will updated some time after the release of a new version on GitHub.
+Login as root and do:
+ +yum-config-manager --add-repo https://opm-project.org/package/opm.repo
+yum install resinsight
+yum install resinsight-octave
+Then you are good, and can start ResInsight by typing: ResInsight
+ +On the command line do:
+ +sudo apt-get update
+sudo apt-get install software-properties-common
+sudo apt-add-repository ppa:opm/ppa
+sudo apt-get update
+sudo apt-get install resinsight
+sudo apt-get install octave-resinsight
+Start ResInsight by typing : ResInsight
For further installation details, see the ResInsight distribution on Opm Project Downloading and Installing.
+The binary distributions does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see +Build Instructions.
+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) :
+ +gconftool-2 --type boolean --set /desktop/gnome/interface/buttons_have_icons true
+gconftool-2 --type boolean --set /desktop/gnome/interface/menus_have_icons true
+This fix was taken from reply number 11 in this thread
+ +octave-cli (for older version of octave use octave)The precompiled octave interface distributed in the tarball is only tested for RedHat 6.
+It is not expected to work for other configurations.
+(ResInsight 1.3.2-dev and earlier, was also tested on RedHat 5)
+
+If you need the octave interface to work on a different OS, you need to build ResInsight yourself.
+See Build Instructions
Uncheck Settings->Display->Enable 3D Acceleration. Disabling this option will cause OpenGL operations to be executed in software, so the the performance of graphics operations in ResInsight will be slower, but will not crash.
+ +Here is a pointer addressing the issue with Virtual Box, this is not testes by us:
+ +https://superuser.com/questions/541537/how-to-solve-issues-with-shader-model-in-virtualbox
+ + + + + + +The binary distribution does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see +Build Instructions.
+C:\Your\Path\To\Octave-x.x.x\bin\octave-cli.exe )A binary package of ResInsight will normally not work with other Octave versions than the one it is compiled with.
+You have to point to the cli binary in the windows octave installation. The octave.exe will not work as it is launching the octave GUI.
ResInsight is a powerful open source, cross-platform 3D visualization, curve plotting, and post processing tool for reservoir models and simulations. +This chapter provides an overview of its functionality and installation.
+ + + + + + + + +ResInsight comes with four navigation modes. The active mode can be selected in the Preferences dialog.
+ +Note that changing the navigation mode applies to the currently active view only, and views created after the change.
+ +These abbreviations are used in the tables below:
+ +| Abbreviation | +Meaning | +
|---|---|
| LMB | +Press the left mouse button | +
| MMB | +Press the middle mouse button or scroll wheel button | +
| RMB | +Press the right mouse button | +
The following applies to all navigation modes:
+ +| Mouse interaction | +Action | +
|---|---|
| RMB single click | +Right-click menu (context menu) | +
| LMB single click | +Update status bar and Result Info | +
| Mouse interaction | +Action | +
|---|---|
| LMB + drag | +Zoom model | +
| MMB + drag | +Rotate model | +
| Scroll wheel | +Zoom to mouse pointer location | +
| RMB + drag | +Pan model | +
| Mouse interaction | +Action | +
|---|---|
| LMB + drag | +Pan model | +
| MMB + drag | +Rotate model | +
| MMB + Shift | +Pan model | +
| Scroll wheel | +Zoom to mouse pointer location | +
| Mouse interaction | +Action | +
|---|---|
| LMB + drag | +Rotate model | +
| MMB + drag | +Pan model | +
| Scroll wheel | +Zoom to mouse pointer location | +
| Mouse interaction | +Action | +
|---|---|
| LMB + drag | +Pan model | +
| MMB + drag | +Zoom to mouse pointer location | +
| Scroll wheel | +Zoom to mouse pointer location | +
| RMB + drag | +Rotate model | +
Feel free to join ResInsight on LinkedIn
+ +By subscribing to the Release Notification you will get notified when new releases are available. +Please use the button below to send a request for subscription mail.
+ + + + + + + + +“I have been using ResInsight now for some time and have stopped using the commercial software as ResInsight is much more responsive and easier to use. It really is an excellent piece of software.”
+ +David Baxendale
+Senior Petroleum Engineering Advisor, RPS Energy
“ResInsight is an excellent tool to visualize simulation results and offers good-looking and illustrative graphs for presentations. I found the integration with Octave especially powerful in my research.”
+ +Tor Harald Sandve
+Researcher, International Research Institute of Stavanger (IRIS)
Equinor ASA has initiated, financed and supervised the development of ResInsight and is using it on a daily basis.
+ResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots.
+ +
The two main windows has a toolbar button each, that directly opens and raises the other window. 
+
+
Each of the windows can also be closed freely, but if both are closed, ResInsight exits.
+ +Each of the main windows has a central area and several docking windows surrounding it. The different docking +windows can be managed from the Windows menu or directly using the local menu bar of the docking window.
+ +Result Info and Result Plot is described in detail in Result Inspection
+ + +Use several Project Trees and Property Editors: +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 Windows->New Project and Property View.
+A selected subset of actions are presented as controls in the toolbar. The different sections in the toolbar can be dragged and positioned anywhere as small floating toolbars. Management of the toolbar is done by right-clicking on the toolbar and then manipulating the displayed menu.
+ +In the main area of the application, several 3D views or plot windows can be open at the same time. One of them will be active and the active view can be either maximized to use the whole main area, or restored so that you can see the open windows.
+ +Standard window management for applying minimized, normal and maximized state is available in the upper right corner.
+ +
Commands to arrange the windows in the standard ways are available from the Windows menu
+ +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.
+ +Toggling a checkbox next to an item in the Project Tree will toggle visibility in the window. Toggling a checkbox for a collection of items will affect the visibility for all items in the collection. 
+
right-click menu commands are also available to do special operations on a selected set of items.
+ +How to interact and manipulate the 3D model is described in Model Navigation
+ +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.
+ +The following Eclipse cases can be imported into ResInsight via the File->Import->Eclipse Cases menu, +see Import Eclipse Cases:
+ +
+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.
+ +
+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
+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 .
+ +
+This is the case type listed in the Plot Main Window, and represents an *.SMSPEC file. These Cases are available for Summary Plotting. See Summary Plots .
+There are only one type of geomechanical cases, namely the ABAQUS-odb case type.
+When ResInsight is compiled with ABAQUS-odb support, *.odb files can be imported by selecting the menu item:
+File->Import->Geo Mechanical Cases->
+ Import Geo Mechanical Model.
The geomechanical cases are sorted into its own folder in the project tree named Geomechanical Models 
+ as opposed to the Grid Models folder where the Eclipse cases and Grid Case Groups resides.
See Build Instructions on how to compile ResInsight with odb-support.
+ +
+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 .
+ +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.
Statistics calculations, octave generated property sets, and SSI-hub imported well paths are saved to a folder named <ProjectFileName>_cache in the same directory as the project file. If you need to move your project, make sure you move this folder along. If you do not, the calculations or well path import needs to be done again.
The *.rsp file is an XML file, and can be edited by any text editor.
+
ResInsight 2018.11 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2018.11 contains a larger number of new and exciting features, some of which are listed below.
+ +
Local Grid Refinement (LGR) can be created based on Eclipse simulations. The refined grids can also be visualised in 3D.
+ +See Completions LGR
+ +
ResInsight lets the user create new/custom well paths by clicking in the 3D view. A self-established well path will behave in the same way as a regular imported well path.
+ + + +
ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D map.
+ +See Contour Maps
+ +
ResInsight can create Well Bore Stability plots for Geomechanical cases. These plots are specialized Well Log Plots and contain a visualization of Formations, Well Path Attributes as well as a set of well path derived curves in two different tracks.
+ + + +
ResInsight can require a considerable amount of memory to hold all the grids and necessary result variables. A Memory Management system is now in place to help the user if available memory is low.
+ + + + + + + + +ResInsight 2019.04 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.04 contains a larger number of new and exciting features, some of which are listed below.
+ +
ResInsight supports the creation of cross plots of two results against each other, with each cell in the grid representing one data point in the plot. The data points can be grouped by a third result, by time step or by Formations, giving a separate color and label for each group.
+ +See Grid Cross Plots
+ +
ResInsight can create plots displaying bubble and dew point pressures, together with initial pressure in model, versus depth. Fluid contacts (GOC and/or OWC) are displayed as annotation lines in the generated plots.
+ + + +
Sub-sections of the Eclipse Grid with Parameters and Faults can be exported to Eclipse ASCII files in order to create new Simulations on the sub-section. These sub-sections can also be refined to a higher resolution.
+ + + +
ResInsight supports interactive modeling of ICD, AICD and ICV. It is possible to export completions to a text file containing the Eclipse input data keywords needed to represent the completions as a Multi Segment Well - MSW.
+ +See Completions and Completion Export
+ +
Annotation objects like text, lines and plolylines can easily be added to a view.
+ +See Annotations
+ +
ResInsight now supports measuring distances and polyline lengths across a Grid.
+ +See Measurements
+ +Several new keyboard shortcuts have been added to ResInsight for convenience. The shortcut can be seen by hovering over tool bar icons to show the tooltip for the given action, or seen in the right-click menu for project tree items.
+ +
+
For instance will the Delete key now delete any deletable item in the project tree and Ctrl-Alt-S/N/W/E/D/U will change the 3d Camera view to South, North, West East, Down and Up respectively.
+ + + + + + + + +ResInsight 2019.08 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.08 opens up a range of new and efficient workflows by adding Python script support in ResInsight.
+ +Basic example on how to update views from Python
+ +import rips
+# Connect to ResInsight instance
+resInsight = rips.Instance.find()
+
+# Check if connection worked
+if resInsight is not None:
+ # Get a list of all cases
+ cases = resInsight.project.cases()
+ for case in cases:
+ # Get a list of all views
+ views = case.views()
+ for view in views:
+ # Set some parameters for the view
+ view.setShowGridBox(not view.showGridBox())
+ view.setBackgroundColor("#3388AA")
+ # Update the view in ResInsight
+ view.update()
+See Python Scripting
+ +It is now possible to launch ResInsight as a console application with no user interface. Some workflows might include servers with no graphics card, and the console mode enables use of ResInsight in this context.
+ + + +
See Summary Plotting
+ + + + + + +ResInsight supports the following type of Eclipse input data:
+ +*.GRID and *.EGRID files along with their *.INIT and restart files *.XNNN and *.UNRST.*.GRDECL files.Release 2018.11 supports import of simulations from Intersect. To be able to import into ResInsight, the Intersect simulation must be exported into Eclipse file format.
+ResInsight offers several ways to import Eclipse (grid) files. Use one of the following commands in the File->Import->Eclipse Cases menu:
+ +*.EGRID or *.GRID Eclipse files for import. Multiple selections are allowed.The Reload Case command can be used to reload a previously imported case, to make sure it is up to date. This is useful if the grid or result files changes while a ResInsight session is active.
+ + +You can select several grid files in one go by multiple selection of files (Ctrl + left mouse button, Shift + left mouse button).
+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
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->Eclipse Cases->
+ 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.
+ +
+ Import Input Eclipse Case and select a *.GRDECL file.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.
+ +
Element property tables in ABQUS input file format can be imported into ResInsight and displayed as Element Results. This can be used to display material properties, or any scalar value on each element.
+ +To view the data as a Color Result select the Result Position: Element ( See Geomechanical Results )
+ +A couple of property names are recognized and treated specially:
+ +A couple of examples on the file format are shown below.
+ +ResInsight searches for the first line containing *Distribution Table, then splits the following line by ,. These entries describes the expected property values to be found in the file.
ResInsight then searches for the data block by ignoring lines
+ +* and ,,When the datablock is found, the part of the line before . is stripped away, and first column is expected to be element ID
** ELASTIC SETTING FOR EACH ELEMENT
+*Distribution Table, name=RSV_Res-1_Elastic_Table
+MODULUS, RATIO
+*Distribution, name=RSV_Res-1_ELASTICS, location=ELEMENT, Table=RSV_Res-1_Elastic_Table
+** Description: Element-by-Element Elastic properties
+, 2.
+Res-1.210, 11198814808.2538, 0.19041
+Res-1.209, 11207002032.1436, 0.19063
+Res-1.208, 11222989223.0933, 0.19104
+Res-1.207, 11202549454.349, 0.19051
+** DENSITY SETTING FOR EACH ELEMENT
+*Distribution Table, name=RSV_Res-1_Density_Table
+Density
+*Distribution, name=RSV_Res-1_DENSITIES, location=ELEMENT, Table=RSV_Res-1_Density_Table
+** Description: Element-by-Element Densities
+, 1.
+Res-1.210, 2500
+Res-1.209, 2500
+Res-1.208, 2500
+Res-1.207, 2500
+ResInsight can be built with support for reading and displaying geomechanical analysis models produced by ABAQUS in the *.odb format. This is only possible if you or your organization has a copy of the ODB-Api from Simulia, and a valid license to use it.
If you have, and would like to a use these features, please see Build Instructions for a description on how to build ResInsight and how to include the support for odb-files.
+ +Geo-mechanical data can be imported using the Import -> Geo Mechanical Cases menu. Here three options are present: Import Geo Mechanical Model, Import Geo Mechanical Model (Time Step Filtered) (both for odb files) and Import Element Property Table.
+ +
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 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.
+ +Pressure and stress are always displayed using the Bar unit.
+ +Other derived results are also calculated, and are described in Derived Results
+ +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.
+ +By choosing the Import Geo Mechanical Model (Time Step Filtered) option, it is possible to limit the amount of time steps that are imported to improve the speed and reduce the memory use. If this option is chosen a tile step filter dialog is shown after selecting the file to import.
+ +
The data can be filtered by skipping Days, Weeks, Months or Years in the top Filter Type drop down list and the range of time steps can be picked in the First Time Step and Last Time Steps lists. Furthermore, the final selection can be fine tuned by selecting or deselecting individual time steps in the Select From N Time Steps list. ResInsight will ignore any data that doesn’t match these time steps and will thus reduce the amount of data imported.
+ + + + + + +
ResInsight is able to import the following type of Eclipse files:
+ +*.GRID and *.EGRID files along with their *.INIT and restart files *.XNNN and *.UNRST.*.GRDECL files.For functionality and import of Eclipse data pertinent to summary vectors and well log data, see Plot Window.
+ +ResInsight can be built with support for geomechanical models from ABAQUS and is also able to import +transient reservoir souring data from the SourSimRL simulation software.
+ +Furthermore, ResInsight supports import of property tables in ABQUS input file format, +observed time history data, and pasting time history data into a summary plot +as described in the subsequent subchapters.
+ + + + + + + + +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.
+ +Importing observed time history data to ResInsight may be performed in two different ways:
+ +The following file types are supported:
+ +
+ Observed Time History Data files will be added to 
+ Observed Time History Data.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”.
+ +
CSV/txt files are generic ascii files where data is arranged in columns. Some variations in formatting is supported, for instance deifferent cell separators, date and time format, decimal separator etc. 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.
+ +
Dialog fields description:
+ +Each column must have a header text, which may be a name/description for the data in the column. By formatting the header text to a valid Eclipse address, ResInsight recognizes the column data and will be able to categorize the data in the same way as grid data. So when plotting these data later, the user will find the data in the correct category in the Summary Plot Editor.
+ +An Eclipse address consists of a vector name and zero or more parameters. The number of parameters are defined by the category of the vector. The category is determined by looking up the category in an internal vector table. A valid standard vector name has 3 to 5 characters. Optionally it may be postfixed by a user defined name of 3 characters. A vector name having both a standard part and a user part must have 8 characters (5+3). In this case, if the standard part has less than 5 characters, it must be padded with underscores up to 5 characters. Example: ‘RPR__WEL’. Vector names having only the standard part are not padded.
+ +Categories:
+ +When ResInsight parses an eclipse address, it first tries to identify an address category by analyzing the vector name, as described above. If no category could be found, the Imported category is used. This category is also used if the address format is wrong (for instance missing parameters) even though the vector name identifies a different category.
+ +Instantaneous vs Accumulated Data
+A valid Eclipse vector having a standard name ending with ’T’ or ‘TH’ are considered accumulated data. In the summary plot, these types of data are plotted slightly different. Instantaneous data are plotted using a stepped curve, while accumulated data are plotted using straight lines between the samples.
Error data
+Any address may have associated error data. Those type of data will have the same address as their associated data, but are prefixed by ‘ER:‘, ‘ERR:’ or ‘ERROR:‘. Example: ‘ERR:FOPT’. It is not possible to select error data explicitly in the plot editor selection fields, but when selecting a vector having associated error data, the error data is plotted as error bars in the summary plot.
Example:
+ +
ResInsight supports a ‘line based’ CSV file format variant as well. As opposed to the normal CSV format, data values are organized in lines. Each line must contain at least a date (and time), a vector address and a sample value. Optionally it may also contain an error value and a comment. The information carried by this format is equivalent to the normal CSV format, it is only a different file layout.
+ +When importing a line based CSV file, no dialog appears. Instead a more stict set of rules apply to this type of files:
+ +The two examples below are equvalent and result in identical data after importing to ResInsight
+ +Line based CSV:
+ +DATE ;VECTOR ;VALUE ;ERROR
+2018-04-16 ;FOPT ;12.5 ;0.45
+2018-04-18 ;FOPT ;8.6 ;0.31
+Normal CSV:
+ +DATE ;FOPT ;ERR:FOPT
+2018-04-16 ;12.5 ;0.45
+2018-04-18 ;8.6 ;0.31
+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.
+ +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.
+ +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 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
+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.
+ +
To plot Observed Time History Data, choose New Summary Plot in the right-click 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. Observed time history data points are plotted without lines by default.
+ + + + + + +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.
+ +
Most of the fields in this dialog are the same as in the CSV/txt import options dialog. Please see that section for documentation on those fields. The fields specific to the paste options dialog are as follows:
+ +ResInsight is able to import transient results from the simulation software SourSimRL to combine reservoir souring simulation data with an Eclipse case for analysis and visualization. +Results from SourSimRL in its sourres binary format can be imported using the SourSim File Name field as shown below:
+ +
Importing such a file will enable result type called SourSimRL as explained in Eclipse Result Types
+ + + + + + +
✓ Open source
✓ Efficient user interface
- ✓ Handles large Eclipse cases
+ ✓ Handles large Eclipse cases
✓ Plotting of summary vectors
- ✓ Embedded Flow Diagnostics
+ ✓ Embedded Flow Diagnostics
✓ NNC visualization
✓ Cell Edge Coloring
@@ -37,24 +1616,1232 @@ overview: true
It's easy and free, both on Linux and Windows:
- Installation →
-
- Sign up to be notified of new releases:
Release Notification →
-
Sign up to be notified of new releases:
+
+ Release Notification →
+
Here are some words from a few of the happy ResInsight users Testimonials →
+Here are some words from a few of the happy ResInsight users Testimonials →
This chapter of the ResInsight documentation describes the following:
+ +See the subsequent subchapters for more information on each topic.
+ + + + + + + + +