Changes between Version 36 and Version 37 of DevelopersCommittee/Agenda/2017-06-27

Timestamp:

2017-07-21T11:25:13+02:00 (7 years ago)

Author:

clevy

Comment:

--

DevelopersCommittee/Agenda/2017-06-27

@@ -41 +41 @@
 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.
@@ -47 +48 @@
 A lot of discussions took place within the group, especially to elaborate important tasks and priorities. Within the GEOMETRIC project now funded, the developments are identified and will start within the next year.
 Le Working Group proposes to be disbanded.
+
+[attachment:DevCommJune2017_WG_PME_MJB.pptx Mike Bell's presentation] 
 
 ==== TOP (C. Ethé, O. Aumont)
@@ -69 +72 @@
 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, approved by Developer's Committee, will be sent (as a final draft) to Steering Committee for information by end of July.
 
 
 === 4) Preparing 2018 and mid-term ===
 ====  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: 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 
+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: WG shoud contribute to choose a unique tool 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: Following mid-term strategy, should focus on the tool to set up NEMO configuration only, leaving aside the coupling module with other models. Objective is to 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. Overlap with Nesting Tools of AGRIF and tools developed for test cases should be clarified by deciding a unique tool for each functionality.
+
+* Robustness and test cases : Very good job to be continued, focusing on the ways to set up, accept and distribute test cases. Same comment as for AGRIF WG
+
+* Data assimilation and interface: 
+
 * Parametrisation of mesoscale eddies: as suggested by WG, it is now disbanded.
+
 * TOP 
+
 * Sea-ice 
-* 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
+
+* Wave coupling:  reorganise this WG to air-sea coupling, including waves (aligned with Chapter 9 of Dev. Strategy document). Proposal for this renewed WG to be presented by E. Clementi and L. Brodeau during next meeting end of the year
 
 ==== First ideas on 2018 Workplan (presented by System Team), and discussion
@@ -88 +99 @@
 
 === 5) Review of the role of Developer’s Committee  ===
+[attachment:NDS_Teams_Working_Groups_MJB.ppt Mike Bell's presentation of the ideas discussed during Enlarged Dev.Com. in Barcelona] 
+
+Discussion and comments:
+Need to take in account carefully the existing resources for development: creating teams will not make development happen. All volunteers for sustainable developement of NEMO are welcome (a clear workflow is in place for this), but new features and improvements of NEMO are de facto created by developers.
+
 * Role of the Committee
+The NEMO Developer's Committee is the Scientific advisory board of NEMO Consortium. The role of the external experts is important and could be enhanced: need for regular attendance of these experts also to the meetings of the Committee. 
+Somme additonnal external experts are proposed: Eric Chassignet
+
 * What is working? 
+ * Creating and ending Working Groups
+ * Building the mid term strategy (Enlarged dev com meeting, writing and updating the strategy document)
+ * Getting the complete view on what is going on through the meetings twice a year
+ * Giving advices on yearly workplan (although messages to SC not really followed up to now)
 * What could be improved? (including link between scientific projects going on and NEMO development workplan)
+Meetings of Developer's Committee are too long (up to now, it seemed important to have information on each group or team (System Team, Working Groups...). The committee proposes to have from now on a subgroup to examine all ongoing actions in order to limit the agenda of the meetings to the points needing discussion. Claire Lévy to propose the organisation, list of members and tasks of this subgroup before next meeting.
 
 
 == List of participants ==
-''Please try to join in one place if connecting from the same city''
 
 || Name || Role || Connecting from ||