SUMTHIN
Recognised by the OPM Flow parserSUMMARYSCHEDULE
Variant 1 — SUMMARY section
This keyword defines a time interval for writing out the SUMMARY data to the SUMMARY file and the RSM file, if the RUNSUM keyword has also been activated in the SUMMARY section. Only the data for the first time step in the time interval is written out and the other time steps are skipped until the next time interval, except for report time steps. Note that report time steps data are always written out regardless of the setting on this keyword. This enables the size of the SUMMARY files to be reduced depending on the size of the time interval. However, the keyword will produce irregular time steps reports of the SUMMARY data.
Notes:
The keyword is terminated by a “/”.
See also the RPTONLY keyword in the SUMMARY section that forces the SUMMARY data to be only written out at report time steps, as opposed to all time steps or SUMSTEP time intervals.
- Records
- Fixed number of records
- Record count
- 1
- Items per record
- 1
Parameters
| No. | Name | Description | Type | Dimension | Field | Metric | Lab | Default |
|---|---|---|---|---|---|---|---|---|
| 1 | TIMEmanual: SUMSTEP | SUMSTEP is a real positive number that defines the time interval for which the first time step of data will be written to the SUMMARY file (and the RSM file if RSM output has been activated). For example, if SUMSTEP is set to 30 days, and if the simulator takes time steps of 0, 5, 10, 16, 24, 30, 40, 45, 60, 90 days. Then the SUMMARY data will be written out at time steps 0, 30, 40 and 60 days. | DOUBLE | Time | days | days | hours | None |
Example
--
-- DEFINE SUMMARY DATA REPORTING TIME STEP INTERVAL
--
-- SUMSTEP
SUMTHIN
30.0 / /
The above example defines the SUMMARY file time step interval to be 30 days for both field and metric units.Manual source: parts/chapters/subsections/11.3/SUMTHIN.fodt
Variant 2 — SCHEDULE section
This keyword defines a time interval for writing out the SUMMARY data to the SUMMARY file and the Atgeirr Rasmussen 2017-09-22T12:19:56.742970000 AFR We don’t write any RSM files (what are those?) RSM David Baxendale 2017-10-02T18:55:45.272000000 DBx Reply to Atgeirr Rasmussen (09/22/2017, 12:19): "..." We should write RSM files, as they contain the production and injection data from the SUMMARY files in ASCII format. Engineers normally load this file into EXCEL to generate plots and economic production forecasts. file, if the RUNSUM keyword has been has also been activated in the SUMMARY section. Only the data for the first time step in the time interval is written out and the other time steps are skipped until the next time interval. This enable the size of the SUMMARY files to be reduced depending on the size of the time interval. However, the keyword will produce irregular time steps reports of the SUMMARY data.
We don’t write any RSM files (what are those?)
Reply to Atgeirr Rasmussen (09/22/2017, 12:19): "..."
We should write RSM files, as they contain the production and injection data from the SUMMARY files in ASCII format. Engineers normally load this file into EXCEL to generate plots and economic production forecasts.
See SUMTHIN – Define SUMMARY Data Reporting Time Stepsin the SUMMARY section for a full description.
- Records
- Fixed number of records
- Record count
- 1
- Items per record
- 1
Manual source: parts/chapters/subsections/12.3/SUMTHIN.fodt