Changes between Version 34 and Version 35 of DevelopersCommittee/Agenda/2017-06-27

Timestamp:

2017-07-20T17:28:47+02:00 (7 years ago)

Author:

clevy

Comment:

--

DevelopersCommittee/Agenda/2017-06-27

@@ -40 +40 @@
 First test cases available in NEMOGCM, so as associated tools to build and use them
 Now need to define the location of all test cases (existing ones build build consortium members, so as future ones coming from the community), so as the acceptable procedure for all to ensure sufficient quality control (including the responsibilities of System Team on one side, and of the developer on the other).
-
+Interest expressed (by D. Marshall) to start using test cases for students.
 ==== Data assimilation and interface ()
 Some inputs have been included in the strategy document, but role and perspectives of this working group are unclear for now, after the decision made concerning TAM, so as the leave of Pierre-Antoine Bouttier from his position.
@@ -50 +50 @@
 ==== TOP (C. Ethé, O. Aumont)
 No new developments for now, but focus on consolidation of modularity with regards to the different BGC models (PISCES, BFM, MEDUSA...)
-A meeting on PISCES development, with representatives of BFM and MEDUSA will take place in PAris beginning of July. Scope of WG may be updated afterwards, so as the corresponding section of NEMO Development Strategy document
+A meeting on PISCES development, with representatives of BFM and MEDUSA will take place in Paris beginning of July. Scope of WG may be updated afterwards, so as the corresponding section of NEMO Development Strategy document
 
 ==== Sea-ice (M. Vancoppennolle)
@@ -69 +69 @@
 The Developer's Committee will write a message to SC (action J. Le Sommer) to try convincing SC to make it open.
 
-Claire Lévy will ensure the draft is complete and fulfils the suggestions and comments of Dev. Committee. AS so, the draft will be considered as approved by Dev. Committee and send (as a draft) to SC for information by end of July.
+Claire Lévy will ensure the draft is complete and fulfils the suggestions and comments of Dev. Committee. As so, the draft will be considered as approved by Dev. Committee and send (as a draft) to SC for information by end of July.
 
 
@@ -75 +75 @@
 ====  Evolutions of Working Groups 
 Developer’s Committee to make recommendations for each Working Group by the end of 2017. If relevant, list of new Working Groups to be created, and selection of their members
-*  AGRIF 
-* Configuration Manager 
-* Robustness and test cases 
+*  AGRIF: need to find a unique place where tools to set up AGRIF configuration are developed: to be discussed with Configuration Manager and Test cases WGs: need to make one choice between nesting tools (needing update), future configuration manager, or tools build for test cases
+* Configuration Manager: Should focus on the tools to set up NEMO configuration only, and define a strategy with existing resources to decide where to drive the future for next generation, starting from SIREN. Same comment as for AGRIF WG
+* Robustness and test cases : Very good job to be continued, focusing on the modality to set up for accepting and distributing test cases. Same comment as for AGRIF WG
 * Data assimilation and interface 
-* Parametrisation of mesoscale eddies 
-Working Group proposes to be disbanded.
+* Parametrisation of mesoscale eddies: as suggested by WG, it is now disbanded.
 * TOP 
 * Sea-ice 
-* Wave coupling
+* Wave coupling:  change this WG to air-sea coupling, including waves (aligned with Chapter 9 of Dev. Strategy document). Details of proposal to be presented by E. Clementi during next meeting end of the year
 
 ==== First ideas on 2018 Workplan (presented by System Team), and discussion
+No time for this point during the meeting, and limited number of ideas from System Team. This point is postponed but list of preliminary ideas  available [attachment:"Ideas for 2018WP.pptx"] here]
 
 === 5) Review of the role of Developer’s Committee  ===