New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
2019WP/ENHANCE-09_Jerome_freesurface – NEMO
wiki:2019WP/ENHANCE-09_Jerome_freesurface

Version 4 (modified by jchanut, 7 years ago) (diff)

--

ENHANCE-4_Jerome_freesurface

The PI is responsible to closely follow the progress of the action, and especially to contact NEMO project manager if the delay on preview (or review) are longer than the 2 weeks expected.

Help

The action has to be detailed briefly in the 'Summary' section for later inclusion in other pages.
Edit the 'Summary' section as with an ordinary wiki page.

  • Italic formatting shows the default values or help.
  • Set specific TracLinks (development ticket and branch).

Out of this, the rest of the page can be edited on-line inside the form fields considering the following color code given hereafter.

Role / Color code

PI(S) Previewer(s) Reviewer(s)

Record your modifications for the section you have edited by clicking on the corresponding button at the end of the section with 'Save ...' button. Just above, the log record will be updated.

The informations inside the form fields and this wiki page itself are stored in 2 separate databases.
As a consequence, there is absolutely no risk to make any modification in the page itself as long as you don't rename the page or modify the source code of {{{#!TracForm ... }}} processors.

Summary

Action ENHANCE-4_Jerome_freesurface
PI(S) Jérôme Chanut

#!td '''Digest''' {{{#!td Improve split-explicit free surface:

  • Tracer conservation issues (all time splitting options do not ensure global and local tracer conservation)
  • Missing correction terms in the barotropic equations relative to internal pressure gradients. This would reduce mode splitting error, hence improve stability
  • Work on the stability of barotropic time stepping (based on INRIA's work) to possibly remove time filtering of barotropic variables.
    This would limit the temporal dissipation and greatly ease online coupling of nested domains at barotropic level (with AGRIF).
}}}
Dependencies Depends on ...
Target started; need to be scientifically reviewed ; can be ready for merge 2017.
Trac Ticket #1959
SVN branch /branches/2017/dev_r8624_ENHANCE4_FREESURFACE
Previewer(s) Gurvan Madec
Reviewer(s) -
Status In progress: an implementation exist
Link ExtractUrl(.)?

#!comment DON'T REMOVE THIS VOID HEADING OR IT WILL BREAK THE INCLUDE FEATURE BETWEEN WIKI PAGES

#!comment DON'T REMOVE THIS VOID HEADING OR IT WILL BREAK THE INCLUDE FEATURE BETWEEN WIKI PAGES

Abstract

This section should be completed before starting to develop the code, in order to find agreement on the method beforehand.

Error: Failed to load processor TracForm
No macro or processor named 'TracForm' found

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.

Error: Failed to load processor TracForm
No macro or processor named 'TracForm' found

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.

Error: Failed to load processor TracForm
No macro or processor named 'TracForm' found

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).

Error: Failed to load processor TracForm
No macro or processor named 'TracForm' found

Once review is successful, the development must be scheduled for merge during next Merge Party Meeting.