[Opm] Opm Digest, Vol 74, Issue 7: Problems running ECLIPSE model using FLOW

OPM User opmuser0 at gmail.com
Wed Apr 27 06:34:47 UTC 2022


Alun,

There are bunch of keywords that are indeed unsupported. Looking at the 
static keywords first:

These keywords are not important and can be ignored.

  *   ECHO: keyword not supported
  *   NOECHO: keyword not supported
  *   NSTACK: keyword not supported
  *   MESSAGES: invalid value '100000' for item 9
  *   GRIDUNIT: keyword not supported
  *   COORDSYS: keyword not supported

This may be important depending on the data

  *   EXTRAPMS: keyword not supported
  *   RPTSOL: keyword not supported
  *   WBP: keyword not supported
  *   WBP9: keyword not supported
  *   EXCEL: keyword not supported - standard RSM file output is
    supported and you get the individual vectors via OPM ResInsight.
  *   FIPOWG: keyword not supported - no work around.

These are important:

  *   MINPORV: keyword not supported
  *   PMAX: keyword not supported
  *   ROCKOPTS: keyword not supported - don't have an option for this
    without knowing what is being used.
  *   PCW: keyword not supported

I would first try and just initialize the model without any of the 
SCHEDULE section keywords first, to see if we can get a STOIIP etc. If 
this works then we can work around the MINPORV, and PCW keywords by 
loading the E100 case into OPM ResInsight and exporting the PORV, 
TRANX/Y/Z and PWC  keywords and then loading then back into OPM Flow. 
You could try the same approach for the other arrays as well if necessary.

If you manage to get the model initialize with similar volumes then one 
has to deal with the SCHEDULE section keywords not supported:

  *   VFPCHK: keyword not supported - no work around, bit may be not
    important.
  *   WDFAC: keyword not supported  - you could try picking up the
    connection factors from E100 and using them. Not sure this will work
    but worth a try.
  *   GRUPNET: keyword not supported - no work around I'm afraid.
  *   WELDRAW: keyword not supported - no work around.
  *   WTEST: invalid value 'PEGDC' in record 1 for item 3 WTEST(TEST):
    only the E (economic) option is currently supported
  *   WVFPEXP: keyword not supported - but has been implemented in the
    developer version, unfortunately this will not be in the 2022-04
    release, but will be in the 2022-10 release.
  *   GCONPRI: keyword not supported - no work around.
  *   PRIORITY: keyword not supported - no work around.

If you have funds then you may wish to consider sponsoring the 
development to implement some of the missing features.

opmuser0 at gmail.com

------------------------------------------------------------------------

On 27-Apr-22 04:18, opm-request at opm-project.org wrote:
> Send Opm mailing list submissions to
> 	opm at opm-project.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://opm-project.org/cgi-bin/mailman/listinfo/opm
> or, via email, send a message with subject or body 'help' to
> 	opm-request at opm-project.org
>
> You can reach the person managing the list at
> 	opm-owner at opm-project.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Opm digest..."
>
> Today's Topics:
>
>     1. Re: Problems running ECLIPSE model using FLOW (Alun Griffiths)
>     2. Issues with two phase upscaling (Alun Griffiths)
>     3. Re: Issues with two phase upscaling (Alf Birger Rustad)
>
> _______________________________________________
> Opm mailing list
> Opm at opm-project.org
> https://opm-project.org/cgi-bin/mailman/listinfo/opm



More information about the Opm mailing list