Introduction To Eclipse
Introduction To Eclipse
Lecture 1
Haval Hawez
E-mail: haval.hawez@koyauniversity.org
1
Contents
Keywords in Sections
Useful Information
2
What is ECLIPSE 100?
• ECLIPSE 100 is a fully-implicit, three phase, three dimensional, general purpose black
oil simulator with gas condensate option.
• ECLIPSE 100 can be used to simulate 1, 2 or 3 phase systems. Two phase options
(oil/water, oil/gas, gas/water) are solved as two component systems saving both
computer storage and computer time. In addition to gas dissolving in oil (variable
bubble point pressure or gas/oil ratio), ECLIPSE 100 may also be used to model oil
vaporizing in gas (variable dew point pressure or oil/gas ratio).
3
How to START?
• To run simulation you need an input file with all data concerning reservoir
and process of its exploitation.
• Input data for ECLIPSE is prepared in free format using a keyword system.
Any standard editor may be used to prepare the input file. Alternatively
ECLIPSE Office may be used to prepare data interactively through panels,
and submit runs.
4
Input Data File
• An ECLIPSE data input file is split into sections, each of which is
introduced by a section-header keyword. A list of all section-header
keywords is given in following, together with a brief description of
the contents of each section and examples of keywords using in file
code.
5
Section-header Keywords
•The list of section-header keywords in proper order:
RUNSPEC
GRID
EDIT
PROPS
REGIONS
SOLUTION
SUMMARY
SCHEDULE
It is recommended that the body of sections which are not frequently
changed be held in separate files which are included in the data using
the INCLUDE keyword.
A data record has to be ended with a slash [/]
6
Section-header Keywords
RUNSPEC
Status: REQUIRED
Title, problem dimensions, switches, phases present,
components etc.
GRID
Status: REQUIRED
The GRID section determines the basic geometry of the simulation
grid and various rock properties (porosity, absolute
permeability, net-to-gross ratios) in each grid cell. From this
information, the program calculates the grid block pore
volumes, mid-point depths and inter-block transmissibilities.
7
Section-header Keywords
EDIT
Status: OPTIONAL
Modifications to calculated pore volumes, grid block centre
depths and transmissibilities.
PROPS
Status: REQUIRED
Tables of properties of reservoir rock and fluids as functions
of fluid pressures, saturations and compositions (density,
viscosity, relative permeability, capillary pressure etc.).
Contains the equation of state description in
compositional runs.
8
Section-header Keywords
REGIONS
Status: OPTIONAL
Splits computational grid into regions for calculation of:
- PVT properties (fluid densities and viscosities),
- saturation properties (relative permeabilities and capillary pressures)
- initial conditions, (equilibrium pressures and saturations)
- fluids in place (fluid in place and inter-region flows)
If this section is omitted, all grid blocks are put in region 1.
SOLUTION
Status: REQUIRED
Specification of initial conditions in reservoir - may be:
- calculated using specified fluid contact depths to give potential equilibrium
- read from a restart file set up by an earlier run
- specified by the user for every grid block (not recommended for general use)
This section contains sufficient data to define the initial state (pressure, saturations,
compositions) of every grid block in the reservoir.
9
Section-header Keywords
SUMMARY
Status: OPTIONAL
Specification of data to be written to the Summary file after each
time step. Necessary if certain types of graphical output (for
example water-cut as a function of time) are to be generated
after the run has finished. If this section is omitted no
Summary files are created.
SCHEDULE
Status: REQUIRED
Specifies the operations to be simulated (production and injection
controls and constraints) and the times at which output
reports are required. Vertical flow performance curves and
simulator tuning parameters may also be specified in the
SCHEDULE section.
10
Section-header Keywords
RUNSPEC section
TITLE title
DX, DY, DZ X,Y,Z-direction grid block sizes for the current box; data is
taken from Isopac map, and geological model from IRAP
13
Section-header Keywords
GRID section
DX, DY, DZ X,Y,Z-direction grid block sizes for the current box; data is
taken from Isopac map, and geological model from IRAP
14
Section-header Keywords
PROPS section
15
Section-header Keywords
PROPS section
16
Section-header Keywords
PROPS section
17
Section-header Keywords
REGIONS section
18
Section-header Keywords
SOLUTION section
19
Section-header Keywords
SOLUTION section
20
Section-header Keywords
SUMMARY section
FOPT Field Oil Production Total
In the data following a keyword, asterisks may be used to signify repeat counts.
A data quantity can be repeated a required number of times by preceding it
with the required number and an asterisk.
There must be no intervening blank spaces next to the asterisk on either side.
For example, the two following cases are equivalent: RPTSCHED
0 0 0 0 0 0 0 0 0 0
See an example 0 2 0 0 2 /
RPTSCHED
11*0 2 2*0 2 /
Comments
• Any lines beginning with the two characters ‘--’ are treated as comments, and will be
ignored by ECLIPSE. Comment lines (and blank lines also) may be inserted anywhere
in the data file. Comments may also be added to the end of lines of data by beginning
the comment with the two characters ‘--’, but in this case the comments must not
contain any quotes. Comments can also be included, without the two characters ‘--’,
on the same line after a slash (/) which is used to terminate a data record.
Default values
• Certain items of data can be defaulted to a built-in default value. The keyword
description will indicate when defaults can be applied. There are two ways of setting
quantities to their default values. Firstly, by ending a data record prematurely with a
slash (/) the quantities remaining unspecified will be set to their default values. Secondly,
selected quantities positioned before the slash can be defaulted by entering n* where n
is the number of consecutive quantities to be defaulted. For example, 3* will cause the
next three quantities in the keyword data to be given their default values. There must be
no blank space between the number and the asterisk. If there is only one item at a time
to be defaulted, then 1* must be entered. An asterisk by itself is not sufficient.
27