New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
DevelopersCommittee/Agenda/2018-01-16 (diff) – NEMO

Changes between Version 45 and Version 46 of DevelopersCommittee/Agenda/2018-01-16


Ignore:
Timestamp:
2018-11-13T16:30:34+01:00 (5 years ago)
Author:
nicolasmartin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevelopersCommittee/Agenda/2018-01-16

    v45 v46  
    1111=== Introduction 
    1212 
    13 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 ] 
     13As 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:NEMO_DevCom_subgroup_Minutes_dec2017.pdf minutes available here ] 
    1414 
    1515=== Discussion on 2017 annual report  
    1616 
    17   The draft of 2017 annual report is available as input to the discussion  [attachment:wiki:DevelopersCommittee/End2017:2017_AnnualReport.docx here] 
     17  The draft of 2017 annual report is available as input to the discussion  [attachment:2017_AnnualReport.docx here] 
    1818Brief overview of the main streams of the year: 
    1919* Goal 1 (short term): Bring the 3_6 release to its final stable state in time for CMIP6 
     
    2323* A major new feature: the new sea-ice framework, in place of LIM2 and LIM3 
    2424* Report to be completed with discussions during this meeting on Working groups 
    25 * Additional work in 2017 to prepare and organise Enlarged DevCom meeting in Barcelona in April 
     25* Additional work in 2017 to prepare and organise Enlarged !DevCom meeting in Barcelona in April 
    2626 
    2727Round table for each of the Consortium and external experts : 
     
    4141 
    4242==== AGRIF  
    43 [attachment:wiki:DevelopersCommittee/End2017:Agrif_dev_com_January2018.pdf Presentation of J. Chanut] 
     43[attachment:Agrif_dev_com_January2018.pdf Presentation of J. Chanut] 
    4444 
    4545Discussion: 
    4646* AGRIF working with TOP is a functionality that has been dropped for now. This should be reconsidered. 
    4747* Usefulness of test cases (vortex used widely for AGRIF). Should become systematic 
    48 * Back port (better) status of AGRIF in the trunk now to 3_6_STABLE? Would need a large amount of work on LIM3 and vvl if is was to be done. No member of DevCom advocates for this back port. 
     48* Back port (better) status of AGRIF in the trunk now to 3_6_STABLE? Would need a large amount of work on LIM3 and vvl if is was to be done. No member of !DevCom advocates for this back port. 
    4949* Nesting tools allow setting up a NEMO configuration with AGRIF zoom. It’s update in order to work with the future release is scheduled, which is indeed an important and priority task, since for now people willing to use AGRIF are stopped by configuration problems. It is indeed critical to have a tool for this. Why doing it with Nesting tools, rather than for example with SIREN? 
    5050Answer: 
     
    5252 * For the future (where a number of AGRIF zooms can be expected) using directly the AGRIF library is seen by WG as the best way to go, since it is more flexible. 
    5353 
    54 * 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 
     54* AGRIF WG is more active which is good news, but one of its active members Tim Graham, 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 
    5555 
    5656'''Recommendations of Developer’s Committee to AGRIF WG:''' 
     
    6161==== Air sea interactions  
    6262 
    63 [attachment:wiki:DevelopersCommittee/End2017:Wave_Air-Sea_WG_20180116_DevCom.pptx Presentation of E. Clementi and S. Masson] 
     63[attachment:Wave_Air-Sea_WG_20180116_DevCom.pptx Presentation of E. Clementi and S. Masson] 
    6464 
    6565Discussion: 
     
    8787 
    8888Since the Developer’s Committee now has a subgroup to discuss things in advance and prepare agenda of meetings, the Devcom asks 
    89 1.      For the next 6 months, this WG is on hold, and decision to be made during next DevCom meeting (mid 2018) 
     891.      For the next 6 months, this WG is on hold, and decision to be made during next !DevCom meeting (mid 2018) 
    90902.      For each of the four existing tools, complete a brief report, for April 2018, using the template sent by subgroup in March. List of reports : SIREN (Julien Paul), Nesting tools (J. Chanut), BDY tools (Stefania Ciliberti), pynemo (J. Harle). Same request to Test case WG on the tools to set up a test case configuration (S. Flavoni) 
    91913.      Since the tools for setting up an AGRIF configuration are the priority of Consortium for now, move the SIREN Actions of 2018 Work plan from “Shared actions”, to “Specific actions for Mercator” 
     
    144144''Organize a workshop with NEMOVAR and NEMO/Assim communities on data assimilation issues, setting the scene for creating a European infrastructure in marine data assimilation. This will include an assessment of the strengths, weaknesses as well as long term evolution plans and future commonalities (e.g. ensemble approaches) of the NEMOVar, NEMO/Assim and SAM tools.'' 
    145145 
    146 •       Some feedbacks on the outcomes of this meeting are expected for next DevCom meeting mid 2018 
     146•       Some feedbacks on the outcomes of this meeting are expected for next !DevCom meeting mid 2018 
    147147 
    148148==== Top discussion group 
     
    186186 
    187187=== NDS document final approval  
    188 The document (attached to this page) has its final content and no red light from Sterring Committee. It is now important to check the final form for a public release. DevCom members are requested to make a final check on the document form if possible and sent suggestions to Claire Lévy before January 23rd, in order to make the public release as soon as possible now. 
     188The document (attached to this page) has its final content and no red light from Sterring Committee. It is now important to check the final form for a public release. !DevCom members are requested to make a final check on the document form if possible and sent suggestions to Claire Lévy before January 23rd, in order to make the public release as soon as possible now. 
    189189 
    190190=== Information on important calls or projects  
     
    225225 
    226226=== Presentation on open development practices elsewhere : Alistair Adcroft  
    227 * [attachment:"wiki:DevelopersCommittee/End2017:Open development_A_Adcroft_presentation.pdf" Presentation of A. Adcroft]  
     227* [attachment:"Open development_A_Adcroft_presentation.pdf" Presentation of A. Adcroft]  
    228228* Discussion 
    229229'''Recommendations of Developer’s Committee:''' 
    230230 
    231231* Continue this discussion and comparison within System Team and with Alistair 
    232 * Results to be presented by System Team at next DevCom meeting 
     232* Results to be presented by System Team at next !DevCom meeting 
    233233 
    234234=== Discussion on 2018 proposed Workplan 
    235235 
    236 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 
     236!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 
    237237''' Recommendations of Developer’s Committee:''' 
    238238