[Opm] Opm Digest, Vol 40, Issue 1

[David Baxendale (Private)]

Lex,

The confusion over this keyword was compounded due to errors in the 
manual for this keyword (the example should use GDFILE not INCLUDE), 
this has been corrected for the 2019-04 release.  As Joakim stated the 
GDFILE keyword will be available in the 2019-04.
ThunderBird Signature File

OPMUSER

------------------------------------------------------------------------
On 05-Apr-19 20:00, 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. Reading EGRID in Flow (Lex Rijkels)
>     2. Re: Reading EGRID in Flow (Joakim Hove)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 5 Apr 2019 10:36:23 +0200
> From: Lex Rijkels <lex.rijkels at gmail.com>
> To: "opm at opm-project.org" <opm at opm-project.org>
> Subject: [Opm] Reading EGRID in Flow
> Message-ID:
> 	<CAB7JViVb_gkTaK0BkX5SQW-Nm6gYeeS3c9yJg4kT8dv_TRiwpA at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Dear Flow community,
> Could you please point out what I am doing wrong when reading EGRID files
> into Flow?
>
> - According to the manual GDFILE will read EGRIDs, but the examples use
> "INCLUDE 'NORNE.EGRID' /". Indeed, Flow gives an error when I use GDFILE
> instead of INCLUDE.
> - But it seems that INCLUDE expects normal keywords. It complains that it
> does not recognize the file header of formatted EGRID files. I've tried
> stripping header info etc, but Flow keeps complaining. Eventually I was
> left with just COORDs and then I got a segmentation fault.
> - If I feed it unformatted EGRID files with INCLUDE, Flow gets stuck on
> reading an empty string and stops. It seems it does not like the binary
> file format.
> - It did not seem to make a difference if I added U or F (or UNFORMATTED)
> to the include statement, as in the GDFILE documentation.
>
> I interpret this as: INCLUDE just expects normal keywords, not EGRID
> information; but the GDFILE command is not recognised. Am I missing
> something?
>
> A bit of extra info:
> - The manual claims that unformatted (binary) EGRIDs generated on Windows
> cannot be read in Unix. That's why I also tried formatted EGRIDs.
> - Interestingly ResInsight does not seem to have problems reading Unix
> EGRIDs into a Windows environment.
> - Is there a way to make Flow read binary Windows EGRIDs? Typically, these
> come from a Windows Petrel installation. Can the binary files be converted?
> (dos2unix does not seem to do the trick)
>
> Thanks a lot for your help,
> Kind regards,
> Lex Rijkels
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 5 Apr 2019 10:43:05 +0200
> From: Joakim Hove <joakim.hove at gmail.com>
> To: Lex Rijkels <lex.rijkels at gmail.com>
> Cc: "opm at opm-project.org" <opm at opm-project.org>
> Subject: Re: [Opm] Reading EGRID in Flow
> Message-ID:
> 	<CALKD1M8GudNANRD49v3MMY8wU-UerKH9ooT89WBVwwrLRnmMnQ at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> INCLUDE expects "normal" ASCII formatted keyword files.
>
> GDFILE will read a EGRID file.
>
>
> Observe however that the GDFILE keyword has quite recently been
> implemented, and it is not yet available in the currently released version
> of flow (2018.10) - it will be available in the 2019.04 version which is
> due quite soon.
>
> Joakim
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Opm mailing list
> Opm at opm-project.org
> https://opm-project.org/cgi-bin/mailman/listinfo/opm
>
>
> ------------------------------
>
> End of Opm Digest, Vol 40, Issue 1
> **********************************



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus