| 1 | = Name and subject of the action |
| 2 | |
| 3 | Last edition: '''[[Wikinfo(changed_ts)]]''' by '''[[Wikinfo(changed_by)]]''' |
| 4 | |
| 5 | The PI is responsible to closely follow the progress of the action, |
| 6 | and especially to contact NEMO project manager if |
| 7 | the delay on preview (or review) are longer than the 2 weeks expected. |
| 8 | |
| 9 | [[PageOutline(2, , inline)]] |
| 10 | |
| 11 | == Summary |
| 12 | |
| 13 | ||=Action || Develop on multi-grid algorithm for passive tracer transport ( coarsening) || |
| 14 | ||=PI(S) || Clément Bricaud || |
| 15 | ||=Digest || Work on the design and starts the development || |
| 16 | ||=Dependencies || If any || |
| 17 | ||=Branch || source:/NEMO/branches/{YEAR}/dev_r{REV}_{ACTION_NAME} || |
| 18 | ||=Previewer(s) || Names || |
| 19 | ||=Reviewer(s) || Names || |
| 20 | ||=Ticket || #XXXX || |
| 21 | |
| 22 | === Description |
| 23 | |
| 24 | {{{#!box width=25em help |
| 25 | |
| 26 | No actions are considered to make the preliminary development on AGRIF to make coarsening with AGRIF |
| 27 | |
| 28 | In IMMERSE, a task has started to runs a coupled OCE+ICE+BGC with 2 seperate executable, coupled with OASIS |
| 29 | |
| 30 | 2 options are possible: |
| 31 | |
| 32 | - OPTION 1: OCE+ICE+BGC in a single executable ( =no OASIS); this the one already developed in NEMO 3.6 |
| 33 | |
| 34 | It can be improve by avoiding duplication of routines ( the rewriting of the code for the 2LTS can help), replace the "e3t_max_crs" by the former "facvol" ) |
| 35 | |
| 36 | It might work also with s-coordinates |
| 37 | |
| 38 | They are probably others ways of improvment |
| 39 | |
| 40 | - OPTION 2 : OCE+ICE+BGC with 2 seperate executables, coupled with OASIS |
| 41 | |
| 42 | In a first time, the coarsened variables can be computed by the algo developped in OPTION 1 |
| 43 | |
| 44 | and OASIS send the coarsened variables to the BGC component, instead of the HR variables |
| 45 | |
| 46 | |
| 47 | In a second time, the coarsened variables can be computed by OASIS |
| 48 | |
| 49 | |
| 50 | |
| 51 | Here the work is to design and develop OPTION 1 and take of the compatibility with OPTION 2 |
| 52 | |
| 53 | |
| 54 | }}} |
| 55 | |
| 56 | ''...'' |
| 57 | |
| 58 | === Implementation |
| 59 | |
| 60 | {{{#!box width=35em help |
| 61 | Describe flow chart of the changes in the code. \\ |
| 62 | List the Fortran modules and subroutines to be created/edited/deleted. \\ |
| 63 | Detailed list of new variables to be defined (including namelists), \\ |
| 64 | give for each the chosen name and description wrt coding rules. |
| 65 | }}} |
| 66 | |
| 67 | ''...'' |
| 68 | |
| 69 | === Documentation updates |
| 70 | |
| 71 | {{{#!box width=55em help |
| 72 | Using previous parts, define the main changes to be done in the NEMO literature |
| 73 | (manuals, guide, web pages, …). |
| 74 | }}} |
| 75 | |
| 76 | ''...'' |
| 77 | |
| 78 | == Preview |
| 79 | |
| 80 | {{{#!box width=50em info |
| 81 | [[Include(wiki:Developers/DevProcess#preview_)]] |
| 82 | }}} |
| 83 | |
| 84 | ''...'' |
| 85 | |
| 86 | == Tests |
| 87 | |
| 88 | {{{#!box width=50em info |
| 89 | [[Include(wiki:Developers/DevProcess#tests)]] |
| 90 | }}} |
| 91 | |
| 92 | ''...'' |
| 93 | |
| 94 | == Review |
| 95 | |
| 96 | {{{#!box width=50em info |
| 97 | [[Include(wiki:Developers/DevProcess#review)]] |
| 98 | }}} |
| 99 | |
| 100 | ''...'' |