Hi, Lex,
Thanks for your feedback. It is not a surprise to me at all if STOP is not well supported in OPM. We have not tested the `STOP` with extensive cases yet. It is not that trivial to fix either and we can not prioritize it at the moment because we are already fully occupied. What do you mean by `losing the FBHP`? If it is something related to output, we might be able to fix it if we understand it. Cheers, Kai ________________________________ From: Lex Rijkels <lex.rijk...@gmail.com> Sent: Wednesday, July 3, 2019 12:39 PM To: Kai Bao Subject: Re: Fw: [Opm] SHUT functionality in 2019.04 Hi Kai, My apologies, I managed to confuse myself while testing this in various ways. Please find my example attached. It is a deck that runs in a few minutes. In the SCHEDULE section I tried to close the well in various ways. - If I SHUT the well, it closes, but I lose the FBHP. - If I STOP it, the well closes in Eclipse, but it continues to produce in Flow - If I ask Petrel to close the well at surface, it adds the STOP command in WCONPROD, but with the previous production rate. In Eclipse this works to stop the well, but not in Flow. - In Flow I can shut in the well by giving it 0 rate in the WCONPROD. Then it keeps reporting the FBHP. So my previous question was incorrect: SHUT seems to work as intended in Flow, but STOP does not seem to work. (I got mixed up because Petrel calls STOP: shut in at surface. I am sorry for wasting your time with my previous question) Am I doing something wrong? You can find the methods to shut in the well by looking for "method" in the DATA file. Thanks a lot for your help, Lex Rijkels On Tue, Jul 2, 2019 at 9:47 PM Kai Bao <kai....@sintef.no<mailto:kai....@sintef.no>> wrote: In case you did not subscribe to the mailing list. I forward my response to the mailing list directly. ________________________________ From: Kai Bao Sent: Tuesday, July 2, 2019 9:44 PM To: opm@opm-project.org<mailto:opm@opm-project.org> Subject: Re: [Opm] SHUT functionality in 2019.04 Dear Lex, I just tested WELOPEN with your setup based on SPE1CASE1, it looks like working properly from my side. As a result, I am not able to re-produce the problem you mentioned. I am not sure if you can share your deck with me? or you can make a small case based one of the SPE cases (like SPE1CASE1) to demonstrate your problem and share with me. When I can re-produce your problem, I can look into for a fix. I attached the case I modified to test WELOPEN for your reference. Cheers, Kai Bao ________________________________ From: Opm <opm-boun...@opm-project.org<mailto:opm-boun...@opm-project.org>> on behalf of Lex Rijkels <lex.rijk...@gmail.com<mailto:lex.rijk...@gmail.com>> Sent: Tuesday, July 2, 2019 5:44:11 PM To: opm@opm-project.org<mailto:opm@opm-project.org> Subject: [Opm] SHUT functionality in 2019.04 Dear OPM community, Has the SHUT functionality maybe changed in version 2019.04 of Flow? I am running a simple well test forecast and my well does not react to: WELOPEN WELLNAME SHUT / / It simply continues producing. It does stop with STOP (but then I lose the reported FBHP) or a rate constraint of 0. Have I missed something in the use of SHUT? Thanks for your help, Kind regards, Lex Rijkels _______________________________________________ Opm mailing list Opm@opm-project.org<mailto:Opm@opm-project.org> https://opm-project.org/cgi-bin/mailman/listinfo/opm Opm Info Page<https://opm-project.org/cgi-bin/mailman/listinfo/opm> opm-project.org<http://opm-project.org> To see the collection of prior postings to the list, visit the Opm Archives.. Using Opm: To post a message to all the list members, send email to opm@opm-project.org<mailto:opm@opm-project.org>. You can subscribe to the list, or change your existing subscription, in the sections below. _______________________________________________ Opm mailing list Opm@opm-project.org https://opm-project.org/cgi-bin/mailman/listinfo/opm
