Beruflich Dokumente
Kultur Dokumente
Reservoir Coupling
Purpose
The Reservoir Coupling option allows the engineer to couple a
defined as SLAVES
The slave processes are activated by the master, and run in
synchronisation with it
The master process imposes production and injection constrains
on the slaves to meet the overall targets
Communication between the processes is handled by the
message-passing system PVM (parallel virtual machine) / MPI
(Message Passing Interface), which must be present on the
system
Slave Reservoirs
Each slave reservoir has its own ECLIPSE input data file
The slave could be a restart run
Each slave must have one or more slave groups - acting as the
path for communicating flow rates and constraints with the master
process
Slave groups can be at different levels. But one slave group
cannot be subordinate to another slave group
Slave
Group
PVM
MPI
Master
Group
same
physical
group
Master Reservoirs
The master has its own ECLIPSE input data file
It can be a reservoir of its own or just a dummy model
PVM
MPI
Master
Group
same
physical
group
R2
2005 Schlumberger Information Solutions. All rights reserved.
R1
The master then decides about the time step length in the usual
way, but subjected to that
it does not overshoot a reporting time step in any of the slave
reservoirs
it keeps the flow rate changes in the slave reservoirs within
acceptable bounds (estimated from the changes over the
previous time step)
2005 Schlumberger Information Solutions. All rights reserved.
injection)
Groups in the slave reservoir that are superior to the slave groups
must not be given any constraints on them
If the slave reservoir has been already given such constraints,
three options are available:
ignore such constraints
honour the constraints
take the minimum of these limits and the targets set by the
master.
network down to the master groups and their own well groups
In each slave reservoir, the slave groups should be defined as
fixed pressure nodes, and the network extended down from them
to the well groups. Any groups superior to the slave groups
should not be part of the network in the slave reservoirs.
Either standard or extended network can be used
Slave
Group
Nodal pressure
PVM / MPI
Master
Group
same
physical
group
node
FA1
COMP-B
COMP-A
SEP
N1
N2
N3
FB1
N4
FB2
FB1
FB2
Coincide with
the source node
Network
2005 Schlumberger Information Solutions. All rights reserved.
Group Hierarchy
Network Balancing
The network should be balanced at each time step (the default in
keyword NETBALAN)
All networks will be balanced simultaneously at each time step of
the master process
At each iteration of the balancing in the master:
Master group nodal pressure -> slave group
Using this pressure as the fixed pressure, slave balances it
own networks to convergence
Slave sends back to the master the flows of the slave groups
Master sums its flows up to the FIELD level, and updates the
nodal pressures
GRUPTREE
R1-A PLAT-A /
R2-A PLAT-A /
R3-A PLAT-A /
R1-B PLAT-B /
R3-B PLAT-B /
/
SLAVES
-- slave slave file
machine
directory
number of
-- name root name host name
of data file Processors
SLV1 SLAV1 *
/usr/models/s1
2 /
SLV2 SLAV2 susie
/usr/models/s2
/
/
DUMPCUPL
U / Unformatted or F /- Formatted
2005 Schlumberger Information Solutions. All rights reserved.
R2-A
R3-A
R3-B
/
SLV1
SLV2
SLV2
Slv Group
fraction
FIELD
R3-A
R3-B
0.1/
0.1 /
0.1/
RCMASTS
10.0 /
ctrl?
3e5 RATE /
phase
100
100
200
LIQ /
LIQ /
LIQ /
GRUPSLAV
-- SG Assoc Qo Qw/Ql Qg Qres Qinj_o Qinj_w Qinj_g
-MG
FIELD R2-A /
/
the filter flags for the rate constraints
are MAST, SLAV and BOTH
The default is MAST
GRUPSLAV
R3-A R3-A /
R3-B R3-B /
/
MASTER F /
especially if the various machines are not of the same type (e.g.
SGI and IBM). It is far easier to run with everything on a single
machine.
Error messages get written to the files /tmp/pvmd.uid, and
/tmp/pvml.uid, where uid is the user id number (to get it type id).
A full list
Hosts.txt
hostname
Hostname
hostname
Hostname
License Sharing
When master and slaves are running on the same host, only one license is
required, IF
The licenses required by the slaves are checked before the keyword
SLAVES in the master run
License checking
Some options are checked in RUNSPEC section, e.g. ENDSCALE for
end point scaling
Some options are checked in SCHEDULE section, e.g. GRUPNET for
standard network, SWINGFAC for gas field options
Use keyword LICENSES to reserve licenses in RUNSPEC section
LICENSES
network /
gasfield /
/
References
ECLIPSE Technical Description
PVM
Reservoir Coupling
Installation Guide
Running the software