Refactored RigWellPath to ensure that a well path points and measured depths
always come pairs, as their usage often relies on both being present.
Fixes#1479.
* Fix overwrite of value thresholds
* Fix performance issue with filtered values
* Add "Delete All Polygons" from the polygon collection
* Add area threshold where user can specify area cutoff
* Remove obsolete base class
* Add conversion between one/zero-based IJK
* Move code to RiaTextStringTools
* Add automatic update of grid cell curves when clicking in 3D view
* Fix missing conversion to QString
* Support loading formation names when importing an ensemble
* Enable support for formation filtering when calculating contour map
* Add option to limit calculation area to a selection of polygons
* Enable time step selections and controls in view
* Support loading just what we need for statistics contour maps by using custom reader settings
* Close case once done with it unless there are active views.
* Add selection of user interface case (for result selection, display of wells, faults...)
* Avoid int overflow for nested progresses by using double
* Improve auto naming
* Misc. UI improvements
INDEX_I INDEX_J INDEX_K are result properties computed by ResInsight. When using opm-common, only active cells are defined. In this situation, the computation fails.
Change the implementation to compute these values only for active cells. This will also improve performance and use less memory.
Write data to welltargetdata.GRDECL in a subfolder of the project. Import this data when project is load. The data in this cache is owerwritten when the project is saved.
Improvements:
* Well Target Candidates: Add filtering by binary result
* Well Target Candidates: make result grid cell count configurable.
* Well Target Candidates: Improve ui ordering.
* Well Target Candidates: compute probability, and simplify vector names.
* Optimization: Avoid expensive unintended duplication of data
The check for fault was removed in 4cf6a26083
This causes wrong visualization when a range filter is active and a fault is present along the filter.
There is some performance issues seen when profiling this code, needs more investigation.
* Show timing for geoBuilder.generateSurface()
* Check state of element vector result before geometry is created
* Improve performance for isFaceVisible
Avoid calling costly function cell() when possible
Remove check on fault geometry as this does not affect the visualization
* Performance: Avoid traversal of all cells when computing visibility
When we have an active cell grid, we can skip checking for inactive and invalid state.
Use the list of active grid cells when looping through cells.
Magne Sjaastad
jonjenssen
Kristian Bendiksen
jonjenssen