`GDFILE`

Recognised by the OPM Flow parserGRID

The GDFILE keyword loads a GRID file that contains the structural data for the grid as a set of topological cuboidal cells, and EGRID files that contain structural and property data. Note OPM Flow only supports reading in EGRID files at this time.

Notes:

The keyword is terminated by a “/”.

See also the GRIDFILE keyword in the GRID section for exporting the GRID and EGRID files from the current simulation run.

Records: Fixed number of records
Record count: 1
Items per record: 2

Parameters

No.	Name	Description	Type	Default
1	`filename` manual: `GRIDFILE`	A character string enclosed in quotes that defines the GRID or EGRID file to be read in and be processed by OPM Flow. Again, OPM Flow only supports reading in EGRID files.	STRING	None
2	`formatted` manual: `FMTOPT`	A defined character string that defines the format of the GRID or EGRID file to be read and should be set to one of the following: FORMATTED: If the file is formatted as ASCII i.e. a text file, as opposed to a binary file. The option can be abbreviated to just the letter F. UNFORMATTED: If the file is in binary format, note this option can be abbreviated to just the letter U. If the variable FMTOPT is omitted then the default is for binary file input for the commercial simulator; whereas OPM Flow derives FMTOPT from the file extension (.EGRID or .FEGRID), making FMTOPT superfluous.	STRING	U

Example

The first example shown below loads the NOR-OPM-A00-GRID.EGRID file in binary format from the same directory as the data file.
--
-- LOAD A GRID FILE
--
GDFILE
'NOR-OPM-A00-GRID.EGRID' /
The next example loads the same EGRID file one directory above from where the data file is located.
--
-- LOAD a GRID FILE
--
GDFILE
'../NOR-OPM-A00-GRID.EGRID' /

Related keywords

Cannot be combined with: COORD, ZCORN

Manual source: parts/chapters/subsections/6.3/GDFILE.fodt