O. Leeuwenburgh

A suggested solution approach: 1. Identify wells that are closer to each other than some threshold value. This would need to be based on similarity of either the full list...

The identification of duplicate wells based on well nodes seems easiest. _well_connections in _from_flow.py returns a dataframe with wells and associated well node coordinates. This dataframe will ultimately need to...

An alternative, possibly easier, solution approach is the following: keep all well nodes, but when creating the network that connects them, use only the unique set of well nodes, associate...

A related issue is that it would be good to know which flow tubes are removed by the various options based in length, angle etc. especially if this concerns tubes...

One issue I see with connecting to e.g. the 25% deepest nodes is that we will also be connecting to injectors. Does it make sense at all to connect to...

Any reason to choose this particular division between the 2nd and 3rd layer (we proposed k=15 before as lowest index for layer 2)? I suggest to explicitly define also other...

I repeat and extend a comment I made in #356: an alternative could perhaps be to first assign volumes to flow tubes, and then to distribute that volume over the...

On further thought, some refinement may be necessary. For example, if all nearest nodes are to the right, any connections to the left would be removed, which may be undesirable....

Result of a new check of this issue:  Above: display of WOPR:D-1H from the Norne full model simulation (line) and measurements used by Flownet (dots and error bars). ...

  The problem is now solved. The solution may not be ideal since it requires the creation of 2 'Schedule' class instances instead of 1: one to create the...