NEXTSTPL
Recognised by the OPM Flow parserSCHEDULE
This keyword defines the maximum time step size the simulator should take for the next time step for all Local Grid Refinements (“LGR”). This keyword can be used to reset the time step for when known large changes to the model are taking place that may result in time step chops. For example, if the reporting time size is using monthly reporting steps via the DATES keyword in the SCHEDULE section, then if for example, a group of wells start production at a given date, then the NEXTSTPL keyword can be used to shorten the next step in all the LGRs in order to avoid a time step chop.
Notes:
The keyword is terminated by a “/”.
See also the NEXT and NEXTSTEP keywords in the SCHEDULE section that are used to control the global grid’s next time step.
This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. See section 2.2Running OPM Flow 2023-04 From The Command Lineon how to control time stepping for OPM Flow.
- Records
- Fixed number of records
- Record count
- 1
- Items per record
- 2
Parameters
| No. | Name | Description | Type | Dimension | Field | Metric | Lab | Default |
|---|---|---|---|---|---|---|---|---|
| 1 | MAX_manual: NSTEP1 | NSTEP1 is a real positive value that defines the maximum length of the next time step. | DOUBLE | Time | days | days | hours | None |
| 2 | APPLY_manual: NSTEP2 | NSTEP2 is a character string that should be set to either NO or YES to state if the NSTEP1 should be applied to future reporting time steps. NO: Means that NSTEP1 should not be applied to subsequent reporting time steps. YES: means that STEP1 should be applied to subsequent reporting time steps. The default value of NO means that NSTEP1 will only be applied once. | STRING | NO |
Example
--
-- NEXT ALL
-- STEP TIME
-- ---- ----
NEXTSTEP
1 'NO' /
Here the next step size for all LGRs is set to one day and should only be used once.Manual source: parts/chapters/subsections/12.3/NEXTSTPL.fodt