Version 4 (modified by cbricaud, 4 years ago) (diff) |
---|
Name and subject of the action
Last edition: Wikinfo(changed_ts)? by Wikinfo(changed_by)?
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.
Summary
Action | Develop on multi-grid algorithm for passive tracer transport ( coarsening) |
---|---|
PI(S) | Clément Bricaud |
Digest | Work on the design and starts the development |
Dependencies | If any |
Branch | source:/NEMO/branches/{YEAR}/dev_r{REV}_{ACTION_NAME} |
Previewer(s) | Gurvan Madec |
Reviewer(s) | Names |
Ticket | #XXXX |
Description
No actions are considered to make the preliminary development on AGRIF to make coarsening with AGRIF
In IMMERSE, a task has started to runs a coupled OCE+ICE+BGC with 2 seperate executable, coupled with OASIS
2 options are possible:
- OPTION 1: OCE+ICE+BGC in a single executable ( =no OASIS); this the one already developed in NEMO 3.6
It can be improved by avoiding duplication of routines ( the rewriting of the code for the 2LTS can help), replace the "e3t_max_crs" by the former "facvol" )
It might work also with s-coordinates, different tracer advections schemes and vertical mixing schemes.
They are probably others ways of improvment
- OPTION 2 : OCE+ICE+BGC with 2 seperate executables, coupled with OASIS
In a first time, the coarsened variables can be computed by the algo developped in OPTION 1
and OASIS send the coarsened variables to the BGC component, instead of the HR variables
In a second time, the coarsened variables can be computed by OASIS
Here the work is:
- to design the implementation and to take care of the compatibility with OPTION 2
- to develop OPTION 1 in a z-coordinate context
- In a first time, implementation will be done in TOP component and tested with a synthetic tracer
- in a second time, the implementation will be done in PISCES
Implementation
...
Documentation updates
...
Preview
...
Tests
...
Review
...