Changes between Version 16 and Version 17 of 2015WP/ZZ_VideoconfOnWPProposal_20nov2014
- Timestamp:
- 2014-11-22T12:52:36+01:00 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
2015WP/ZZ_VideoconfOnWPProposal_20nov2014
v16 v17 30 30 || Tim Graham || Met-Office || NEMO System Team || 31 31 || Andrew Coward || NOC || NEMO System Team || 32 || Gurvan Madec || NOC &CNRS || NEMO System Team ||32 || Gurvan Madec || CNRS || NEMO System Team || 33 33 || George Nurser || NOC || NEMO System Team || 34 34 || Hedong Liu || NOC || NEMO System Team || … … 40 40 NEMO System Team develops the NEMO reference through a yearly workplan, i.e. a list of actions, with PIs..., and working groups. [[BR]]Actions listed in workplan = code developed, whereas Working Groups discuss to make scientific and/or technical choices and set up appropriate development actions.[[BR]]There is only 1 NEMO reference, so that there must be some coherency in all this. 41 41 42 At this point, discussions took place within NEMO System Team to elaborate the proposal. [[BR]]Gen ral context:42 At this point, discussions took place within NEMO System Team to elaborate the proposal. [[BR]]General context: 43 43 44 * we now have the Development Strategy” document, finalised last june, identifying for mid-term what we agreeded on, and what remains in discussion45 * 2015 will be a “special year”, because we needed a STABLE release in May for CMIP6 44 * We now have the Development Strategy” document, finalised last june, identifying for mid-term what we agreeded on, and what remains in discussion 45 * 2015 will be a “special year”, because we needed a STABLE release in May for CMIP6= nemo_v3.6_STABLE 46 46 47 47 Objective of this meeting: get the inputs and comments from the NEMO community on the 2015 workplan proposal. For now, it is on the wiki, in 2 parts: 48 48 49 * the so called “Shared Actions”, core of the proposal, as the 2015 contribution to the evolution of NEMO defined in the Development Strategy, to be achieve by the NEMO System Team (experts), i.e. the “minimum 1 man-year” per institution of the Consortium49 * the so called “Shared Actions”, core of the proposal, as the 2015 contribution to the evolution of NEMO defined in the Development Strategy, to be achieved by the NEMO System Team experts, i.e. the “minimum 1 man-year” per institution of the Consortium 50 50 * the “per institution” pages: additional work, with additional manpower, to achieve some developments of specific interest for an institution of the consortium 51 51 52 As first overview, the Shared actions pages lists 7 paragraphs:52 As first overview, the Shared Actions page lists 7 sections: 53 53 54 54 * AGRIF … … 66 66 67 67 == Discussion == 68 * What about the developments, updates... in the coupling interface, needed for CMIP6? They are not listed in 2015 workplan [Uwe Fladrich, EC-EARTH]68 * What about the developments, updates... in the coupling interface, needed for CMIP6? They are not listed in 2015 workplan [Uwe Fladrich, EC-EARTH] 69 69 70 Those are expected to be finalised now (i.e. for the Merge Party in december 2014), or at the latest very beginning of 2015. Planning is to have the nemo_v3.6_STABLE release ready and fully validated for CMIP6 mid-2015.70 Those are expected to be finalised now (i.e. for the Merge Party in december 2014), or at the latest very beginning of 2015. Planning is to have the nemo_v3.6_STABLE release ready and fully validated for CMIP6 by mid-2015. 71 71 72 * Could we have some details on HPC actions in 2015? What about HPC-2 action (MERCATOR - M. Chekki)? Are there some plans to look in details at relative performance of routines in NEMO? [Kim Serradell Maronda, BSC]72 * Could we have some details on HPC actions in 2015? What about HPC-2 action (MERCATOR - M. Chekki)? Are there some plans to look in details at relative performance of routines in NEMO? [Kim Serradell Maronda, BSC] 73 73 74 M. Chekki will be PI of an action on HPC still to be defined. 74 M. Chekki will be PI of an action on HPC still to be defined.[[BR]]BSC is more then welcome to contribute ''(to be discussed between BSC and S. Masson, leader of HPC working group)'' 75 75 76 BSC is more then welcome to contribute ''(to be discussed between BSC and S. Masson, leader of HPC working group)''77 76 * What about OpenMP? [J. Holt] 78 77 … … 81 80 * How and when is the validation for CMIP6 going to take place? [Uwe Fladrich, EC-EARTH] 82 81 83 There are 2 target configurations (with a few decinations for each): ORCA1 and ORCA025. A first set of validation will take place during the first semester of 2015.[[BR]]For ORCA1, 2 focal points/actions are identified:[[BR]]- ORCA1_LIM3_PISCES: Action "ROBUST-2" - NEMO ready for ESMs-CMIP6: ORCA1_LIM3_PISCES (C. Lévy); and some work on ORCA1_CICE at NOC (A. Coward).[[BR]]- ORCA025: Actions "ROBUST-3" Met-Office and "ROBUST-4"at Mercator.[[BR]]Comment by J. Le Sommer: there are 2 levels of testing: a "functionnal" level, and some work need to asses solutions. For the second one, a dedicated session will take place dunring the next DRAKKAR meeting, and an ocean medel development group meeting (CLIVAR) will take place afterwards also in Grenoble (in order to define a common forcing strategy). [[BR]]Comment by Uwe Fladrich: EC_EARTH will continue to assess results and send feedback through tickets82 There are 2 target configurations (with a few declinations for each): ORCA1 and ORCA025. A first step of validation will take place during the first semester of 2015.[[BR]]For ORCA1, 2 focal points/actions are identified:[[BR]]- ORCA1_LIM3_PISCES: Action "ROBUST-2" - NEMO ready for ESMs-CMIP6: ORCA1_LIM3_PISCES(C. Lévy); and some work on ORCA1_CICE at NOC (A. Coward).[[BR]]- ORCA025: Actions "ROBUST-3" Met-Office and "ROBUST-4"at Mercator.[[BR]]Comment by J. Le Sommer: there are 2 levels of testing: a "functionnal" level, and some work need to assess solutions. For the second one, a dedicated session will take place during the next DRAKKAR meeting, and an ocean model development group meeting (CLIVAR) will take place afterwards also in Grenoble (in order to define a common forcing strategy). [[BR]]Comment by Uwe Fladrich: EC_EARTH will continue to assess results and send feedback through tickets 84 83 85 84 * What about the list of reference configuration? Could there be a coupled configuration (i.e. ESM-like) in the list? [Uwe Fladrich, EC-EARTH] 86 85 87 The list of reference configurations is relatively small today and should remain so: the role of reference configuration are: to help new users setting up a first use of NEMO (all inputs files are available, results of functionnal tests are available), and allow through the SETTE tool, to assess and validate a new development/release of NEMO. Thus, reference configurations are an important amount of work for System Team. This work should not be increased too much: main responsibility of System team is to develop the platform.[[BR]]Aside from the reference confiurations, there is the alternative to set up a "Shared configuration": shared by a community, but no support from System Team.[[BR]]It is a very relevant idea to have tools to assess coupling interface in NEMO. S. Masson gives some information on the ongoing work: in 3.6_STABLE, coupling interface will we compiled, even id not used (using fake OASIS routines), and a kind of "fake_ESM" is envisaged to be able to set up preliminary tests at run-time.[[BR]]Comment from U. Fladrich: EC_EARTH would be interested to take responsibility of an ESM shared configuration with NEMO ''(to be discussed further between EC-EARTH and System Team)''86 The list of reference configurations is relatively small today and should remain so: the objectives for reference configuration are: to help new users setting up a first use of NEMO (all inputs files are available, results of functionnal tests are available); and to allow through the SETTE tool, to assess and validate a new development/release of NEMO. Thus, reference configurations are an important amount of work for System Team. This work should not be increased too much: main responsibility of System team is to develop the platform.[[BR]]Aside from the reference configurations, there is the alternative to set up a "Shared configuration": shared by a community, but no support from System Team.[[BR]]It is a very relevant idea to have tools to assess coupling interface in NEMO. S. Masson gives some information on the ongoing work: in 3.6_STABLE, coupling interface will we compiled, even id not used (using fake OASIS routines), and a kind of "fake_ESM" is envisaged to be able to set up preliminary tests at run-time.[[BR]]Comment from U. Fladrich: EC_EARTH would be interested to take responsibility of an ESM shared configuration with NEMO ''(to be discussed further between EC-EARTH and System Team)'' 88 87 89 88 * What about the diagnostics when using variable volume layers? [O. Marti] 90 89 91 Indded, all diagnostics should be carefully reviewed when activating vvl since layers thickness now change every time step. This is going to be critical for users: concerns not only on-line diagnostics and outputs (done in the reference by System team), but also all the off-line diagnostics build by users. Need to send information, and maybe training for users.90 Indded, all diagnostics should be carefully reviewed when activating vvl since layers thickness now change every time step. This is going to be critical for users: concerns not only on-line diagnostics and outputs (done in the NEMO reference by System team), but also all the off-line diagnostics build by users. Need to send information, and maybe training for users. 92 91 93 92 * LSCE is going to develop the accounting of water isotopes in NEMO. Could this task be added in the workplan? [O. Marti] 94 93 95 96 97 Interesting to share this information within the community, and see if other groups are interested. If additional tasks where to be envisaged in workplan, need to come with additional manpower in System Team, especially when the development is possibly quite intrusive. ''To be further elaborated with System Team.'' 94 Interesting to share this information within the community, and see if other groups are interested. If additional tasks where to be envisaged in workplan, need to come with additional manpower in System Team, especially when the development is possibly quite intrusive. ''To be further elaborated, and agenda to be looked at, with System Team.'' 98 95 99 96 * I'm very interested in action "ROBUST-5 CMCC": OBC with BDY for biogeochemistry, when will it be ready? [J. Holt] 100 97 101 A. Lovato, PI of this action, says will be ready next march. J. Holt says it's perfect.98 T. Lovato, PI of this action, announce it will be ready by next March. J. Holt says "it's perfect".
