Visualization of simulation group tree

[anders-kiaer]

Screenshot from prototype:

Code from prototype (not fully ported to React/Dash): #243.

Some additional input/comments:

• Thickness is used to visualize rates (i.e. in practice, the edge thicknesses will increase "down river" - the screenshot above is using unrealistic dummy data).
• Is there some way (edge color, other way) to also visualize pressure drop over edges (reducing the need of mentally interpreting pressure node values as in the prototype).
• Might want to show more "metadata" at the leafs/wells (BHP, BHP9 etc.).
• Might want to visually signal that parts of the group tree is not present in all realizations in an ensemble (and that the backend providing the data performs the "union" of the structures across realizations).
• Might want to select a given node in the tree as temporary "top node" in order to make more horizontal space (useful for deep trees).
• Tree structure and "rate + pressure" data typically have different order of magnitudes time resolution (tree structure more constant, while rate + pressure typically change every time step, which could be of the order of one day). I.e. might want to slightly decouple them in the input data structure (both for rendering/update performance, and data transfer).

[anders-kiaer]

Maybe useful references: https://d3-wiki.readthedocs.io/zh_CN/master/Tree-Layout/ https://www.d3-graph-gallery.com/dendrogram.html https://bl.ocks.org/mbostock/4339083

[asnyv]

Comment: I would prefer to BHP, BP9 and etc to be their own leaves (we have all the information: rates (from well rates), pressures and so on. Actually it might only be relevant from the backend / data input, the component doesn't have to care about this at all?

[lindjoha]

Other things we can include as options:

• Display VFP table number on the edges
• Display Well control mode (WMCTL) on the well nodes
• Split gas rates in reservoir gas and gas lift

[nicktalb]

Relative v Absolute values Would it be useful to be able to show relative allocations rather than absolute for each parent and children set? For large networks you could end up with very thick lines to the left and thin to the right. For ensemble based visualizations where stats are required it would be near impossible to see the variation over the ensemble if percentiles were visualized as bands.

OWG combined You could have RGB lines with relative thickness. This might only make sense for history and/or single realization. For ensembles it is probably too much information?

[aprilzhang]

Just to copy some comments from Knut:

There are many use cases for such data tree:

• For visualization components selecting which wells,
• For creating sections need not the only list of wells but also the order of wells
• Creating well lists for use in modelling.

1) Most modelling create a well list called Used in model not used in model 2) Many history matching projects have similar list wells used in history match, wells not used in history match

There are some important features of such trees one could consider:

• Can wells be in several branches at the same time, i,e can wells be in two groups at the same time
• does the well groups support ordering of the wells