Eclipse output file data.

1. Runspec section.

2. GRID section.

3. PROPS section.

4. REGIONS section.

5. SOLUTION section.

6. SUMMARY section.

7. SCHRDULE section.

Return.


1. Runspec section.

The Runspec section is the first section of eclipse data input file. It contains the run title, start date, units, various problem dimensions ( numbers of blocks, wells, tables, etc.), flags for phases present and option switches. It may be preceded only by comments and keywords INCLUDE, ECHO, NOECHO, COLUMNS, FORMFEED, OPTION, DEBEG and LOAD. The Runspec section must always be present, unless the LOAD keyword is used to restart run from a SAVE file which contains the Runspec data.

The Runspec section consists of a series of keywords, which turn on the various modelling options, or contain data (eg. Problem dimensions). For keywords that have associated data, the data record must be terminated by a slash (/). If a data record is terminated early with a slash, the remaining data items are set to their default values. For most runs, the majority of the data items can be defaulted.

Example of keywords.

TITLE: this define a run title, which will be included in the print file headers. The syntax is different from other keywords, that no quotes or slash (/) are required, and the line after the keyword is read exactly as given.

DIMENS: grid dimensions.

The data consists of three items, describing the basic size of the simulation grid. the data must be terminated by a (/). There is no default, it is an error not to supply the grid dimensions.

1. NDIVIX: Number of cells in the X or R direction.

2. NDIVIY: Number of cells in the Y or THETA direction.

3. NDIVIZ: Number of cells in the Z direction.

RADIAL:

The keywords indicate (R, THETA, Z) geometry is to be used for the simulation. The default is to used Cartesian geometry. The radial grid completes a full circle. The Radial keyword has no associated data.

NONNC: Disallow non neighbour connections.

This indicates that non neighbour connections are not allowed, the default is to allow non neighbour connections.

FIELD: field units are to be used.

This indicates that field units are to be used. The keyword has no associated data.

EQLDIMS: dimension of equilibration tables.

The data consists of up to five items, specifying the dimensions of equilibration table.

1. NTEQUL : the number of equilibration regions entered using EQLNUM in the regions section. Different equilibration regions may be used to initialise different parts of the reservoir which are not in mutual hydrostatic equilibrium, default : 1.

2. NDPRVD : The number of depth nodes in any table of pressure us depth constructed internally by equilibration algorithm, default: 100.

3. NDRXVD: The maximum number of depth nodes in any table entered in the SOLLUTION section, default: 20.

4. NTTRVD: The maximum number of table of initial tracer concentration versus depth ( keyword TVDP in the SOLLUTION section). Default: 1.

5. NSTRVD: The maximum number of depth nodes in any table of initial tracer concentration versus depth (keyword TVDP in the SOLLUTION section). Default: 20.

TABDIMS: table dimensions.

The data consists of up to eight items, describing the sizes of saturation and PVT tables used in the run, and also the number of fluid -in-place regions. The data must be terminated by a slash (/).

1. NTSFUN: The number of saturation tables entered using SGFN in the PROPS section. (Different PVT table may be used in different parts of the reservoir). Default: 1.

2. NTPVT: The number of PVT tables entered using SGFN in the PROPS section. (Different saturation tables may be used in different parts of the reservoir). Default: 1.

3. NSSFUN: The maximum number of saturation nodes in any saturation table. Default: 20.

4. NPPVT: The maximum number of pressure nodes in any PVT table. Default: 20.

5. NTFIP: The maximum number of FIP regions defined using FIPNUM in the REGIONS section is specified by item 1 in the keyword REGIONS. Default: 1.

6. NRPVT: The maximum number of R, nodes in a live oil PVT table or Rv nodes in a wet gas PVT table. Default: 20.

7. Not used.

8. NTENDP the maximum number of saturation end-point versus depth tables is specified by item 3 in keyword ENDSCALE, but may also be entered here for compatibility with the ECLIPSE simulator. Default: 1. 

Back.


2. GRID section.

The grid section defines the geometry of the computational grid and various rock properties (porosity, absolute permeability, net-to-gross ratios) in each grid block. From this information ECLIPSE calculates the grid block pore volumes, mid-point depths and inter-block transmissibilities.

The reservoir geometry may be set using keywords CART or RADIAL in Runspec to either Cartesian (X,Y,Z) or Radial (R,Theta,Z). And may be specified in either two ways:

Block Centred Geometry: where the blocks are horizontal and all eight corners are right angles. Each block is defined by the dimensions of its three sides and the depth of the top surface.

Corner point Geometry: Where the locations of the all eight corners are provided independently and there is no requirement that all the angles of the block are right angles.

 All depths and ticknesses are measured along the Z axis, which is taken to be vertical, with larger values indicating greater depths.

Examples of keyword.

DX (DY) : X (Y) direction grid block sizes for the current input box. Must be set in some way.

DXV : Vector of X direction grid block sizes or use DX.

DR (DTHETA) : R (Theta) direction grid block sizes for the current input box in the Radial block.

PORO: grid block porosities for the current input box. Must be set in some way.

PERMX (PERMY, PERMZ): X (Y, Z) direction permeabilities. etc.

Back.


3. PROPS section.

 The PROPS section of the output data contains pressure and saturation dependent properties of the reservoir fluids and rocks. The data input in multi-tabular keywords, with only one entry of any keyword being accepted. The number of tables of each type is specified in the Runspec section of data. The correct number of tables must be supplied. The Runspec section will also specify the maximum size of each table. When multiple tables are entered after a keyword, each table is terminated by a slash (/).

The data must contain: surface densities of the fluids, data to calculate the reservoir fluid densities and viscosities, the rock compressibility, and relative permeabilities and capillary pressures as a function of saturation.

The minimum set of keywords required in PROPS section is:

GRAVITY or DENSITY for surface gravities/densities.

ROCK for rock compressibility ( unless using the rock compaction option).

PVTO or (PVCO and PMAX) if live oil is present.

PVDO or PVCDO if dead oil is present.

RSCONST or RSCONSTT if dead oil is used to model oil having a constant dissolved gas concentration.

PVTG if wet gas is present.

PVDG or PVZG if dry gas is used to model gas having a constant vaporised oil concentration.

PVTW if water is present.

SWOF if both water and oil are present.

SGOF or SLGOF if both gas and oil are present.

SOF3 or SOF32D for oil in a 3-phase run.

SOF2 for oil if present in 2-phase run.

SGFN for gas if present.

SWFN for water if present. 

Example of keywords:

ADD Adds specified constants to specified arrays in the current box.

DIFFC Molecular diffusion coefficients for each PVT region.

IMPCVD Variation of maximum capillary pressure values with depth for the imbibition curve.

IMPTVD Imbibition end point saturation values vs depth.

KRG Scales gas relative permeability values at a maximum gas saturation, for cells in the current input box.

KRGR Scales gas relative permeability values at residual oil saturation, for cells in the current input box.

KRO Scales gas relative permeability values at a maximum oil saturation, for cells in the current input box.

KRW Scales gas relative permeability values at a maximum water saturation, for cells in the current input box.

KRWR Scales gas relative permeability values at residual oil saturation, for cells in the current input box.

MSFN Relative permeability curves for miscible displacement.

PCG Scales the maximum gas capillary pressure, for cells in the current input box.

PCW Scales the maximum water capillary pressure, for cells in the current input box.

PCMAX Maximum pressure expected in the simulation.

ROCK Rock compressibility.

SGFN Gas relative permeability and capillary pressure as function of Sg.

SGL Connate gas saturation for grid cells in the current input box.

SWFN Water relative permeability and capillary pressure as function of Sw.

SOF2 Oil relative permeability as a function of So in two phase system. etc.

Back.


4. REGIONS section.

The REGIONS section divides the computational grid into regions for:

If there is no REGIONS section, ECLIPSE puts all grid blocks into a single region for all the above operations.

Examples of keywords.

BOUNDARY Defines section of grid for which output maps are required.

IMBNUM Imbibition table region for every grid block in the current input box (if using the hysteresis option).

IMPORT Import binary data geometry by the GRID program. etc.

Back.


5. SOLUTION section.

The SOLUTION section contains sufficient data to define the initial state (pressure, saturations, Rs, Rv) of every grid block in the reservoir. This data may make any one of the following forms:

Equilibration: Initial pressures and saturations are computed by ECLIPSE using data entered with the EQUIL keywords.

Restart: The initial solution may be read from a restart file created by an earlier run of ECLIPSE. The name of the restart file is entered using the RESTART keywords.

Enumeration: The user specify the initial solution for rvery grid block using the keywords PRESSURE or the other variables.

Examples of keywords.

PRVD Pressure vs depth.

SGAS Gas saturation in every grid-block.

SWAT Water saturation in every grid-block.

Rv Vapour oil-gas ratios in every grid-block.

Rs Solution gas-oil ratios in every grid-block.

Back.


6. SUMMARY section.

The SUMMARY section specifies a number of variables which are to be written to summary files after each time step of the simulation. The graphics post-processor may be used to display the variation of variables in the summary files with time and with each other. If there is no SUMMARY section, ECLIPSE does not create any summary files.

Example of variables.

FOPR, GOPR, WOPR Field, Group and Well Oil Production Rate.

FWPR, GWPR, WWPR Field, Group and Well Water Production Rate.

FGPR, GGPR, WGPR Field, Group and Well Gas Production Rate.

FOPT, GOPT, WOPT Field, Group and Well Oil Production Total.

FOIR, GOIR, WOIR Field, Group and Well Oil Injection Rate.

FLPR, GLPR, WLPR Field, Group and Well Liquid Production Rate.

FOPV, ROPV, BOPV Field, Region and Block Pore Volume containing Oil.

A fresh summary file is created at each report time. They have names like BASE.S0011 which is the summary file containing data for all time steps in the period between reports 10 and 11 in a run whose file-name is 'BASE'. 

Back.


7. SCHEDULE section.

 The SCHEDULE section specifies the operations to be simulated (production and injection controls and constraints) and the time at which output reports are required.

Vertical flow performance curves and simulator turning parameters may also be specified in this section. All keywords in this section are optional, except for those necessary to define the status of the wells, and the END keyword which should mark the end of the scheduling data.

To define a well, the following keywords must be used in the stated order:

1. WELSPECS to introduce the well.

2. COMPDAT to specify its completion data.

3. either: WCONPROD production controls, if the well is a producer.

WCONINJE injection controls, if the well is an injector.

WCONHIST flow rates, if the it is a History Matching well.

 Any other keywords that refer to a particular well must be positioned after the well and its connections have been defined.

 Examples of keywords.

WELSPECS Introduces new wells and specifies some of their general data, including the group to which they belong.

VFPPROD Supplies a production well VFP table. VFP tables are required only if there are tubing head pressure targets or limits.

VFPINJ Supplies a injection well VFP table. VFP tables are required only if there are tubing head pressure targets or limits.

Back.