Supply_reservoir_boundary
Contents
Data Structure: Supply_reservoir_boundary |
|
Description |
Defines a boundary inlet/outlet connected to a fluid reservoir |
Usage |
Supply_reservoir_boundary NUM=ival where ival is the data structure number |
Description |
Overview A supply reservoir boundary condition may be applied to both liquid (nearly incompressible) and gas (compressible) phases. The supply reservoir is associated with geometry entities in the model that define the inflow or outflow area. In 2-D these correspond to a single or series of geometry lines and in 3-D a single or series of geometry surfaces. This is achieved by assigning a History_surface data structure to the supply boundary. In addition to defining the supply boundary geometry the surface history outputs the integrated data associated with the supply boundary; e.g. flux, reservoir pressure, etc.
Notes •Prescribed pore pressure boundary conditions are automatically set for all nodes corresponding to the supply reservoir boundary. •Both incremental (end of step) and iterative (every iteration) update of the pore pressure on the supply reservoir boundary may be utilised. In some cases an iterative update can result in quite a large number of iterations without a large benefit in accuracy. In these cases the incremental update may be much more efficient. Iterative update is the default setting. •Several Supply_reservoir_boundary data structures may be specified.
Examples demonstrating the usage of Supply_reservoir_boundary include: •Civan_2d3n_001.dat •elts_2d4n_014h.dat •elts_3d8n_014a.dat
|
 | Name Name of supply reservoir |
| Reservoir_volume Initial reservoir volume |
| Reservoir_pressure Initial reservoir pressure |
| Reservoir_temperature Initial reservoir temperature |
| Singlephase_fluid Single phase fluid ID number |
| History_surface History set number |
| Iterative_update_flag Nonlinear Flag (0-incremental update, 1-iterative update) |