Version 47 (modified by nicolasmartin, 3 years ago) (diff)

2017 Workplan

NEMO is a shared, sustainable, and state-of-the-art software for research and operational oceanography. Its development is defined in a yearly workplan.
Since 2014, the long term evolution is designed in the NEMO Development Strategy document.

The next 2 sections describe the 2017 workplan.

Shared Actions

Shared Actions contains the workplan's core: the development priorities for all NEMO consortium's institutions which are expected to be directly related to the long term goals.

AGRIF \\(''!2017WP/AGRIF-*'') Configuration Manager \\(''!2017WP/CONFIGMAN-*'') Enhancement \\(''!2017WP/ENHANCE-*'') HPC \\(''!2017WP/HPC-*'') Robustness \\(''!2017WP/ROBUST-*'') = Wave Coupling \\(''!2017WP/WAVE-*'')

Specific Actions

Specific Actions contains the other planned developments for the year, as agreed by all consortium members

CMCC actions? \\(''!2017WP/CMCC-*'') CNRS actions \\(''!2017WP/CNRS-*'') INGV actions \\(''!2017WP/INGV-*'') Mercator Océan actions? \\(''!2017WP/Mercator_Ocean-*'') Met_Office actions \\(''!2017WP/Met_Office-*'') NOC actions \\(''!2017WP/NOC-*'')

      Overall status

      'Type: Task'
      'Milestone: 2017 WP'

      AGRIF-1 / Met Office-7 - Vertical grid refinement using AGRIF (2015)
      ENHANCE-01 New website
      ENHANCE-03 New Users area in Trac
      HPC-08 — 3D lbc_lnk argument with any size for the 3rd dimension
      HPC-09_Gurvan — ZDF restructuration with reduced number of lbc_lnk call
      ROBUST-8_AndrewC-MPP_no_ghost development branch
      ROBUST 10 Unify MPPINI
      ENHANCE14 dev_r8329_ENHANCE14_SAL branch development
      TO DO list for the end of the 2017 merge party
      SVN mime-type for namelists to enable syntax highlighting
      NOC-2_JamesH-SCO_ISF development branch
      AGRIF3 Jerome-vvl
      Wave coupling branch - New Stokes drift profile and wind stress
      Merge of Met Office 2017 branches
      Wetting and Drying
      Merge of MERCATOR 2017 branches
      Merge Met Office & Mercator 2017 branches

      Add an action

      Append your action(s) to the list by initiating 2 resources to track and archive your development work: a wikipage to describe and follow the ongoing work through different steps, and a ticket to gather the group discussion and monitor the overall workplan progress.

      To create a new page, you'll need to log in or create an account first.


      • Wikipage name pattern:
        {WG for shared or INSTITUTE for specific actions}-{action number}_{PI(S)}-{keyword(S)}

      Ticket fields setting

      • 'Type: Task', 'Milestone: 2017 WP' and 'Version: trunk' by default
      • 'Cc': add email(s) of people outside NEMO ST for further notification.
      • 'Component': the area the change is being targeted for.

      The other fields in the ticket (e.g. 'Priority', 'Keywords') should also be set appropriately.

      See the instructions page to learn how to implement a development work in NEMO.