-
Notifications
You must be signed in to change notification settings - Fork 41
Intersection component
Knut Midtveit edited this page Mar 12, 2021
·
26 revisions
To Repository: To input data format specification: To story board:
- As geoscientist I like to see an arbitrary cross section through the model, and also cross section defined by well trajectory
- As geoscientist I like to see the distribution of Horizons and faults across above mentioned cross sections
- As geoscientist I like to see the well markers and zone logs on cross section in order to validate the models
- As geoscientist I like to see where the models do not fit to well markers or zonelogs
- As geoscientist I like to see where the perforations are in the cross section for a well
- As geoscientist I like to see a seismic cube in the background and/or a 3D grid parameter in the background for a given run/realization
Assumptions:
- Intersection definition is done upfront as polyline (series of X,Y) from a well trajectory or any other dataobject
- In a addition to Polyline there is z min z max
- Well trajectory projected on intersection is given by Trajectory Z for each intersection pillar
- Investigate the use of Deck GL or use https://equinor.github.io/esv-intersection/storybook/master/?path=/story/complete-example--intersection
- Depth line from faulted or not faulted horizons with selected color
- Fill between horizon lines according to Stratigraphy colors
- Prediction error (1 standard deviation) as dashed line for each Horizon (HUM in prediction mode output)
- Well markers as circles
- Zonelog
- TVD and
- Horizons for an ensemble (many runs/realizations)
- Seismic cross section for one run/realization, with run selector
- Grid properties with time slider for one run/realisation with run selector
- MD thickmarks along well
- Grid properties shown between predicted depth Horizons
- Cross section with two way time for Horizons and for wells (require Time depth table for trajectory)