Giter VIP home page Giter VIP logo

Comments (3)

asnyv avatar asnyv commented on September 20, 2024

A more concrete specification:
Some points are repeated from the initial issue text above.

  • Wells are (plotted) as vertical wells.

    • Note: Wells that are "undulating" in stratigraphy can still be plotted vertically after the regular stratigraphy. We are mainly after which formations they are completed in, not which order they come in.
  • Layers have identical thickness

  • Layer coloring should be configurable, so that a natural grouping of stratigraphy gets a consistent coloring (Not ideal in the sketch).

    • An example from the sketch would be that Garn 4.X followed one color trend (dark to light of a base color), Garn 3.X a new one and so on.
  • Two options for selection of time:

    • A two-sided slider to limit the time span plotted (wells and completions may vary over time). All wells with completions that have been open at any time within the time selection should be included (even though they might have been defined earlier). OK to only plot completions that have been open in the interval, and not plot shut completions.
      Too find producing wells in a time interval (even if only as cross-flow).
    • A single date/timestep: All wells that exist with completions, either open or shut, at that specific time.
  • A multi-select filter for different layers (e.g. only show wells completed in at least one of the selected layers).

  • Choose how wells are distributed along "x axis".

    • Grouped per segment/region
    • Grouped based on shallowest formation it is completed in (so after stratigraphy, not necessarily absolute depth)
    • Injector group / producer group / plugged group
    • All wells
    • Then, within each group either:
      • Alphabetical / alphanumeric
      • Chronologically after when first completion was opened (if different between realizations: earliest time of opening)
  • Color completion by its state: Black for open, strong red for shut (shut completions only relevant for single timestep).

    • How to handle different states of individual completions between realizations: suggest hatching between black and red, more red -> more realizations shut.
  • How to handle completions that only exist in a subset of realizations: narrower wellbore (see sketch)

  • Additional information like ensemble statistics (% of realizations open, average kh and etc) available on hover.

  • Was suggested during scoping meeting to visualize towards cohiba zone log misfit, exact specification of that not functionality not ready yet. Should not be required input from the user side, as users may not have such a log for their model.

Note: Some users might define all wells at beginning of simulation as shut, and then open them when needed. Should therefore consider wells that have not had any open completions prior to the selected time (interval) as "not existing" (not drilled).

Datainput:

  • Completion data as function of time, e.g. through ecl2df as mentioned above
  • A mapping from layer numbers to formations (possibly with a grouping of formations for coloring)

image

It could also at some point be interesting to get to a separate, more detailed, well views on click, e.g. launching other compenents like:

  • a zone contribution plot (inflow/injection rate into each zone) at a locked timestep, would require simulated connection production data as input.
  • log view
  • intersection

Hence, it is necessary that clicking and selecting individual well paths to make an action like that is possible.

from webviz-subsurface-components.

anders-kiaer avatar anders-kiaer commented on September 20, 2024

Another potential feature: Show well status overall e.g. at well head in some way (open, closed, shut)?


This can be taken from the Eclipse keyword WSTAT on the backend side... this will include also automatically shut wells during simulation:

Well State Indicator:
1.0 = PROD (Producer),
2.0 = INJ (Injector),
3.0 = SHUT (Shut for reasons other than priority control),
4.0 = STOP (Stopped for reasons other than priority control),
5.0 = PSHUT (Priority Shut),
6.0 = PSTOP (Priority Stop).

from webviz-subsurface-components.

Midtveit avatar Midtveit commented on September 20, 2024

test comment from Knut

from webviz-subsurface-components.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.