Well status showing as 'STOP' in schedule file

[equinor]

Well status showing as 'STOP' in schedule file

[edubarrosTNO]

I did some research here, and here is what I thought about:

1. Are we sure that WSTAT information is output in the summary file of Eclipse / OPM-Flow? I found no reference to it in the OPM-Flow documentation manual. In the log-file of the OPM-Flow simulation it is printed that Summary keyword 'WSTAT' is unhandled.
2. In the Eclipse manual I found that WSTAT, Well State Indicator: The output is rendered as mnemonics in the .RSM file.
3. As far as I know, the .RSM file is not yet supported by OPM-Flow. And even if it is, I do not think that libecl can read .RSM files. I guess we would have to write separate scripts for that.
4. Of course, we could try to think of an alternative way of extracting dynamic information about the OPEN/SHUT status of the wells.

[anders-kiaer]

Writing WSTAT output is not supported by OPM Flow (yet), but Eclipse supports it. So currently the Eclipse input case to FlowNet needs to be simulated with Eclipse (and with WSTAT in SUMMARY section). Then you get standard summary vectors of the format WSTAT:WELLNAME with integer values.

FlowNet itself of course still can use Flow (as WSTAT is only needed when reading/parsing the initial input case).

Can you verify that your Eclipse input case has WSTAT:* vectors in its UNSMRY?

[olwijn]

I have re-run the Brugge case with WSTAT exported. I will share it with you.

[edubarrosTNO]

Thanks, it seems to work now. It's a pity that it needs to be re-run in Eclipse because we don't have Eclipse in our VM's.
I will close this issue for now. We keep working towards the Brugge predictions