Peter Verveer

I have added these 5 examples to the test for the C function that parses these strings, and they work fine. One of the following things could be going on:...

It seems to be number 2. `subst_list_add_from_string` receives a modified string. Somewhere the arguments are split and then put together again, incorrectly.

It turns out that when the config file is read, the lines are split by space and double quotes (`"`) are removed. Later when a `FORWARD_MODEL` key is detected, the...

This is related to a newer issue that would resolve this with a broader solution: #9537

I have now updated the code to address the length/depth situation so that non-vertical wells are now handled properly. I have tested this against the WELSEGS/COMPSEGS keywords generated by Resinsight,...

Hi @GitPaean, Sure, I am open to changing the design. Let me discuss it with my colleagues at TNO and we will get back to you.

We just had a short discussion, some of the main points we have: 1. WELSEGS offers indeed the flexibility to define segments as you like. We were not trying to...

> 1. how to decide how many segments along the wellbore? We are using the approach that ResInsight has for exporting COMPSEG/WELSEGS keywords. Basically we calculate intersections with the cells...

> > We are using the approach that ResInsight has for exporting COMPSEG/WELSEGS keywords. Basically we calculate intersections with the cells and add a segment to each cell. Currently that...

> > > thanks for the information. to be honest, this types of multi-segment wells can hardly be called multisegment wells and hard to tell what benefit it can bring....