search

equinor / webviz-subsurface

Webviz-config plugins for subsurface data.
https://github.com/orgs/equinor/projects/24
GNU General Public License v3.0
55 stars 59 forks source link

`StructuralUncertainty` feature requests #793

Open asnyv opened 2 years ago

asnyv commented 2 years ago

Suggestions for multiple new features in the StructuralUncertainty plugin, we can split them into multiple issues later, using this issue as a starting point for discussions.

  1. Support for wellpaths per realization: For wells that are not drilled yet, it is quite common to include a form of "geosteering" when you have a model with structural uncertainty. A simple example is "snapping" in RMS. For QC of this process, it would be useful to be able to define a "local wellfolder" in addition to the global, so that you could see how the "geosteered" well(s) fits the horizons of the different realizations (and in that case, it would also be nice to plot both relative to the actual realization and vs statistics, and/or a ref/non-HUM horizon).
  2. A better way to step through realizations: Currently cumbersome to use the modal pop-up and choose single realizations, especially if you want to step realization by realization. Related to the point above where I would like to step through wells per realization. Would then also be nice to connect the stepping both to the intersection view and (at least) one of the maps (e.g. if you have the realization map in one of the map views, and mean/non-HUM in the other, with the diff in the third)
  3. Possibility to co-visualize multiple sets of horizons without defining them as the same attribute: Examples are HUM-horizons, horizons from erosion, horizons made from the grid, horizons for fluid contacts and probably more.
  4. The realization filter is a bit confusing. The filter is placed as a separate top level in the menu structure, but seems to only affect the intersection and not the map view? Either it should be placed under the intersection controls, or the maps should also be connected to the filter. But I guess the realization filter/selection would anyways need a revisit as part of point 1. and 2.
asnyv commented 2 years ago

@tnatt @HansKallekleiv I am open for a chat regarding this if you have time some day 😊 Maybe also a bit relevant in connection with a new intersection component in webviz-subsurface-components?