New URL for NEMO forge!

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.
2017WP/ENHANCE-14_Jerome_SAL – NEMO

Version 4 (modified by cbricaud, 6 years ago) (diff)



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.


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.


Action ENHANCE-14_Jerome_SAL
PI(S) Jerome Chanut, Ariane Koch-Larrouy


Tidal modelling: implementation of Self Attraction and Loading (SAL)

Self Attraction and Loading effects represent the modification by tides of the earth gravity field through mass redistribution. Accounting for this is particularly important to obtain accurate representation of tides at the global scale.
This can be achieved in numerical models by adding an additional term to the existing astronomical potential. The exact computation of this term (which depends on the model tidal solution) is particularly expensive on a numerical point of view and is not part of this implementation.
We will provide here the proper interface in the tidal module and user interface as well to read the SAL potential from external models (TPXO for instance).
The possibility to use a simple "linear" approximation from the sea level anomaly, a commonly used alternative, will also be implemented.

Dependencies Depends on ...
Target Expected end 2017: development/running OK; expected to by done for Merge Party next decemberPriority or deadline
Trac Ticket #XXXX
SVN branch [source:/branches//2017/dev_r8329_ENHANCE14_SAL dev_r8329_ENHANCE14_SAL
Previewer(s) Names
Reviewer(s) Names
Status Pending/In progress/Postponed/Ready
Link ExtractUrl(.)?


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.


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.


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


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.