Changes between Version 33 and Version 34 of DevelopersCommittee/Agenda/2018-01-16

Timestamp:

2018-01-23T11:46:20+01:00 (6 years ago)

Author:

clevy

Comment:

--

DevelopersCommittee/Agenda/2018-01-16

@@ -5 +5 @@
 [[PageOutline(2-3, , inline)]]
 
-== Subgroup work
-
-As decided during last meeting, the NEMO Developer's Committee subgroup has been initiated in order to build a reduced agenda focusing on the points for which a discussion during the meeting is useful. This subgroup met in December 2017, [attachment:wiki:DevelopersCommittee/End2017:NEMO_DevCom_subgroup_Minutes_dec2017.pdf minutes available here ]
 
 == Agenda ==
@@ -75 +72 @@
 
 == Meeting Minutes ==
+=== Introduction
+
+As decided during last meeting, the NEMO Developer's Committee subgroup has been initiated in order to build a reduced agenda focusing on the points for which a discussion during the meeting is useful. This subgroup met in December 2017, [attachment:wiki:DevelopersCommittee/End2017:NEMO_DevCom_subgroup_Minutes_dec2017.pdf minutes available here ]
 
 === Discussion on 2017 annual report 
@@ -116 +116 @@
 * AGRIF WG is more active which is good news, but one of its active members TimGraham, just left. Will his work time on AGRIF be replaced (question to Mt-Office and System team)? No answer at this point. Must be on the agenda of next June’s meeting
 
-'''Recommendations of Developer’s Committee to WG:'''
-
+'''Recommendations of Developer’s Committee to AGRIF WG:'''
+* The WG now has a clear view on the priorities for NEMO-AGRIF development
+* Ensure the availability of a tool to set up NEMO configurations with AGRIF is a high priority for 2018
 
 
@@ -128 +129 @@
 * D. Marshall: the merging of vertical mixing (TKE GLS and OSMOSIS)is not mature for now, at least concerning OSMOSIS. Should maybe be envisaged later on
 
-'''Recommendations of Developer’s Committee to WG:
+'''Recommendations of Developer’s Committee to Air-sea interactions WG:
 1.      Add list of members of this new WG in minutes of this meeting
 2.      Clarify for next meeting (mid 2018) schedule of ALBATROS project contributions, their status (starting release, status of validation, of documentation) in the next 2 years. 
@@ -252 +253 @@
 
 
-=== Information on XIOS and OASIS: possible evolutions, convergences, sustainable resources for development and support 10 mn
-
-=== Presentation on open development practices elsewhere : Alistair Adcroft 20 mn
-
-=== Conclusions 10 mn
-
-''These conclusions will include
-* Advice of the Committee on 2017 work and 2018 proposed work plan
-* Possibly message(s) to Steering Committee''
-
-=== 2018 agenda of Working groups (to be completed by WG leader before/after the meeting) 
-
-  ''List of questions the WG is targeting/expecting to answer:''
+=== Information on XIOS and OASIS: possible evolutions, convergences, sustainable resources for development and support 
+XIOS (Input/output component used in NEMO, developped at IPSL) and OASIS (coupler, developped at CERFACS) are two major features needed by NEMO. 
+They are prerequisites for NEMO (as for other components of Earth System Models). It is therefore critical to be sure of sustainable resources for their development and support. Question has been asked by the subgroup to their leader (Yann Meurdesoif for XIOS, and Sophie Valcke for OASIS). 
+
+==== XIOS
+Resources where up to now ensured by IS-ENES2 and the ANR Convergence projects (as stated in the answer from IPSL in 2013), both ended now. There is no answer for the near future, so as no governance for now.
+
+==== OASIS
+* Governance set up in 2017: First meeting of Users Group and Advisory board
+* Concerning the sustainable resources, Sophie Valcke answered:
+
+''We stress here that for the 2018-2021 period the funding of these developments will come from CNRS (3/4 FTE), Cerfacs (1/2 FTE), the ESiWACE CoE (6 pms total), and possibly IS-ENES3 EU project ). The commitment of CNRS and Cerfacs can be considered stable: in practice, it ensures active user support to the community and the maintenance of the actual code with the possibility of minor upgrades. 
+Additional developments will require additional funding and the only source of such additional funding seems to be EU research infrastructure projects (like IS-ENES3) or French national projects (like a CONVERGENCE follow-up). Other funding models were analysed and proposed to the community but none was considered practical. 
+Such efforts have been successful for the past 20 years and, even if there is obviously no guarantee for the future, Cerfacs commits to keep on seeking such additional EU or national funding.''
+
+
+=== Presentation on open development practices elsewhere : Alistair Adcroft 
+* Presentation of A. Adcroft
+* Discussion
+'''Recommendations of Developer’s Committee:'''
+
+* Continue this discussion and comparison within System Team and with Alistair
+* Results to be presented by System Team at next DevCom meeting
+
+=== 2018 WP
+DevCom approves the proposed work plan so as its priorities on validation and documentation in the perspective of the new NEMO release announcement by mid 2018
+''' Recommendations of Developer’s Committee:'''
+
+* Following decision for Config Manager, move Config Manager development actions from Shared actions to specific Mercator ocean action
+* Approval on priority to Validation and documentation actions to be produced during first semester 2018
+
+
+=== Conclusions 
+
+Message to prepare for Steering Committee
+* Annual report and WP2018 approved
+* XIOS (support and no answer to Dorotea)
+* Make SC aware on difficulties about version used in operation versus version used for developments
+* Need to endorse new NDS now and make it public
+* AGRIF resources with Tim Graham’s departure is a question to be solved
+* Different projects need contact points (see question addressed to Mercator)
+
+