Version 14 (modified by gm, 7 years ago) (diff) |
---|
ENHANCE-5_Gurvan — RK-3 time stepping
Summary
Action | ENHANCE-5_Gurvan — RK-3 time stepping |
PI(S) | Gurvan Madec |
Digest | Introduce an optional RK3 time-stepping scheme. The scheme will:
As such a change will impact many module of OPA, it has been preferred to develop the RK3 version in a separate directory, RK3_SRC, put at the same level as OPA_SRC and being a copy of OPA_SRC as starting point. In addition to the RK3 scheme, a Forward-Bacward Scheme (FBS) will be introduced. The goals associated with FBS are the following:
In practice the work done in 2017 is :
Postponed to 2018 workplan:
|
Dependencies | no |
Target | 2017 merge party |
Trac Ticket | #1911 |
SVN branch | dev_r7881_ENHANCE09_RK3 |
Previewer(s) | Names |
Reviewer(s) | Names |
Status | To be developed |
Link | ExtractUrl(.)? |
Abstract
This section should be completed before starting to develop the code, in order to find agreement on the method beforehand.
Once the PI has completed this section, he should send a mail to the previewer(s) asking them to preview the work within two weeks.
Preview
Since the preview step must be completed before the PI starts the coding, the previewer(s) answers are expected to be completed within the two weeks after the PI has sent his request.
For each question, an iterative process should take place between PI and previewer(s) in order to reach a "YES" answer for each of the following questions.
Once all "YES" have been reached, the PI can start the development into his development branch.
Tests
Once the development is done, the PI should complete this section below and ask the reviewers to start their review in the lower section.
Review
A successful review is needed to schedule the merge of this development into the future NEMO release during next Merge Party (usually in November).
Once review is successful, the development must be scheduled for merge during next Merge Party Meeting.