Reservoir_control_data
Contents
Data Structure: Reservoir_control_data |
|
Description |
Reservoir -> Parageo control dat structure |
Usage |
Reservoir_control_data NUM=ival where ival is the data structure number |
Description |
Overview Reservoir_control_data defines control data for time step and output required to couple ParaGeo with an external resrvoir flow simulator. Currently, this functionality is limited to coupling Intersect (IX) and ParaGeo. When coupling ParaGeo with a reservoir simulator generally only the grid for the reservoir will exist and the data from this grid will be mapped to specific formations (groups) in ParaGeo.
|
 | Control_title Control data name |
Usage |
||||
|
||||
Description |
||||
Defines a name for the Control data / simulation stage (maximum 64 characters).
|
| Solution_algorithm Solution algorithm for explicit and implicit fields |
Usage |
||||
|
||||
Description |
||||
The Solution_algorithm defines the solution algorithm to be used for the explicit and implicit fields. Valid values are:
• 1 - Transient dynamic algorithm for the explicit field (default) • 7 - Implicit nonlinear steady state solver
Explicit solution algorithm: Transient dynamic algorithm (Solution_algorithm =1) This is a standard explicit dynamic forward marching algorithm. The critical time step is computed automatically and the initial time step is by default set to: Δtinit =fcritΔtcrit where fcrit is the factor of critical time step specified via the Factor_critical_time_step keyword. In addition to the factor of critical time step (which is set by default if not specified) the key data for this algorithm is: •the termination data specified by the Termination_time and Maximum_number_time_steps keywords •the output control data for information to the screen, plot file and restart file
Implicit solution algorithm: •Solution_algorithm = 7 is multi-step nonlinear solution with the Newton Raphson method using either direct or iterative solvers defined in Solver_control.
|
| Target_number_timesteps The target number of time steps for each flow step |
Usage |
||||
|
||||
Description |
||||
The target number of time steps for each flow step (default 120). This parameter is in conjunction with Max_step_change_factor to set the target time step for the geomechanical field.
|
| Initial_time Initial time for the analysis (default 0.0) |
Usage |
||||
|
||||
Description |
||||
Specifies that the simulation starts from a specific reference time. Generally Initial_time is not specified and is set to 0.0 by default
|
| Initial_time_increment Initial increment size |
Usage |
||||
|
||||
Description |
||||
Initial increment size Δtinit(inc) in an incremental analysis. The default initial increment size is: Δtinit(inc)=0.05*tterm where tterm is the termination time for the control
|
| Minimum_time_step Minimum time step that terminates the analysis |
Usage |
||||
|
||||
Description |
||||
Minimum time step below which the analysis is terminated. If the minimum allowable time step is not specified then the default value is 0.0; i.e. no termination based on time step size.
|
| Factor_critical_time_step Factor of critical time step for computation of time step |
Usage |
||||
|
||||
Description |
||||
The dynamic solution algorithm is conditionally stable and the time step must be equal or below the critical value Δtcrit which is automatically computed. Practically, the critical time step can only be computed approximately and to ensure stability the time step is set to a factor times the critical value; i.e. Δtnext =fcritΔtcrit where fcrit is the Factor_critical_time_step.
Notes •The default values of the factor of critical time step is fcrit = 0.7 •In problems where contact surfaces are defined, lower values of Factor_critical_time_step may be required to ensure stability (e.g. 0.25)
|
| Maximum_number_time_steps Maximum number of steps for control |
Usage |
||||
|
||||
Description |
||||
Defines the maximum number of steps, or increments, for the current control stage.
|
| Termination_time Termination time for control |
Usage |
||||
|
||||
Description |
||||
Defines the termination time for the current control stage.
|
| Duration The duration for the control step |
Usage |
||||
|
||||
Description |
||||
Defines the duration of the current control stage. If the duration is specified then the Termination time for control is automatically set to the current time + the duration.
|
| Output_frequency_plotfile Output step frequency to plot file |
Usage |
||||
|
||||
Description |
||||
Defines the number of steps (or increments) between two consecutive outputs to plot file. If Output_frequency_plotfile is set to - 1 the output to plot file will be performed at the end of the current control stage.
|
| Output_time_plotfile Output time frequency to plot file |
Usage |
||||
|
||||
Description |
||||
Defines the time between two consecutive outputs to plot file. If Output_time_plotfile is set to - 1 the output to plot file will be performed at the end of the current control stage.
|
| Screen_message_frequency Output step frequency to screen data |
Usage |
||||
|
||||
Description |
||||
Defines the number of steps (or increments) between two consecutive outputs of screen data.
|
| Screen_message_time Output time frequency to screen data |
Usage |
||||
|
||||
Description |
||||
Defines the time between two consecutive outputs of screen data.
|
| Output_frequency_restart Output step frequency to restart file |
Usage |
||||
|
||||
Description |
||||
Defines the number of steps (or increments) between two consecutive restart file outputs (in other words, it defines the frequency in number of steps for update of the ModelName.rst file). If Output_frequency_restart is set to a value of - 1 a restart file for the end of the current control stage will be created with name ModelName_stage_No.rst , where No is the number of the current control stage within the analysis.
|
| Output_time_restart Output time frequency to restart file |
Usage |
||||
|
||||
Description |
||||
Defines the time between two consecutive restart file outputs (in other words, defines the time needed for each update in the ModelName.rst file). If Output_time_restart is set to a value of - 1 a restart file for the end of the current control stage will be created with name ModelName_stage_No.rst , where No is the number of the current control stage within the analysis.
|
| Start_date Start time and date for simulation |
Usage |
||||
|
||||
Description |
||||
Simulation start time in format: "dd-mmm-yyy hh:mm:ss"
|
| Production_Start_date Start time and date for production |
Usage |
||||
|
||||
Description |
||||
Start date for two-way couplingin format: "dd-mmm-yyy hh:mm:ss". By default the production start date is defined by the Start_date
|
| Production_Start_time Production Start time |
Usage |
||||
|
||||
Description |
||||
Start time for two-way coupling in days. By default the production start time is defined by the Start_date or Production_start_date if specified
Notes •if Production_Start_date is specified then Start_date must also be specified
|
| Output_dates List of output dates |
Usage |
|||||||||||||||
|
|||||||||||||||
Description |
|||||||||||||||
list of output date/times in format: "dd-mmm-yyy hh:mm:ss"
|
|||||||||||||||
| Output_times List of output dates |
Usage |
|||||||||||||||
|
|||||||||||||||
Description |
|||||||||||||||
List of output times relative to the start time in days. If Output_dates are specified in addition to Start_date Output_times will be automatrically constructed.
|
|||||||||||||||
| Ixf_filename IXF file name for simulation |
Usage |
||||
|
||||
Description |
||||
IXF file name for simulation. If specified than the start and output dates will be read from the file
|
| Point_value_variables List of element variables |
Usage |
|||||||||||||||
|
|||||||||||||||
Description |
|||||||||||||||
List of element variables and state variables to be computed
|
|||||||||||||||
| Point_value_output_flag Output level for point values |
Usage |
||||
|
||||
Description |
||||
Output level for point values
|