Changes between Version 5 and Version 6 of 2020WP/TOP-03_cbricaud_CRS
- Timestamp:
- 2019-12-20T15:34:50+01:00 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
2020WP/TOP-03_cbricaud_CRS
v5 v6 16 16 ||=Dependencies || If any || 17 17 ||=Branch || source:/NEMO/branches/{YEAR}/dev_r{REV}_{ACTION_NAME} || 18 ||=Previewer(s) || Gurvan Madec 19 ||=Reviewer(s) || Names||18 ||=Previewer(s) || Gurvan Madec, Marc Stringer || 19 ||=Reviewer(s) || Marc Stringer || 20 20 ||=Ticket || #XXXX || 21 21 … … 25 25 26 26 In IMMERSE, a task has started to runs a coupled OCE+ICE+BGC with 2 seperate executable, coupled with OASIS 27 28 29 The previous implementation ( in NEMO 3.6 ) has been use by Sara Berthet in CNRM ( https://doi.org/10.1029/2019MS001644 ) with PISCES and is in integration in NEMO-MEDUSA at UKMO-NOCS. 30 31 A reference paper for the description of the method has been subimitted to GMD (NEMO special issue) 27 32 28 33 2 options are possible: … … 36 41 They are probably others ways of improvment 37 42 38 - OPTION 2 : OCE+ICE+BGC with 2 sep erateexecutables, coupled with OASIS43 - OPTION 2 : OCE+ICE+BGC with 2 separated executables, coupled with OASIS 39 44 40 45 In a first time, the coarsened variables can be computed by the algo developped in OPTION 1 … … 48 53 '''Here the work is''': 49 54 50 - to design the implementation and to take care of the compatibility with OPTION 255 - to design the implementation, in particular to avoid the duplication of routines and to take care of the compatibility with OPTION 2 51 56 52 57 - to develop OPTION 1 in a z-coordinate context … … 58 63 - in a third time, the implementation will be done in PISCES. This part is not expected in 2020. 59 64 65 - OPTION 2 will be treated after, when the separation of executables will be implemented in NEMO 4 reference version. 60 66 61 67 === Implementation