Roadmap

The next stable release of NEMO reference will be the 3_6_STABLE including all recent developments fully validated for CMIP6.

2016WP

Workplan content

2016 Work plan

Last edited LastModified()?

NEMO is a shared, sustainable, and state-of-the-art software for research and operational oceanography. The development of NEMO is defined in a yearly workplan. This page describes the 2016 workplan.
Since this year, the long term evolution is designed in the NEMO Development Strategy document
The 2016 workplan "Shared Actions" are expected to be directly related to the long term goals.

SHARED actions - this pages contains the workplan's core: the development priorities for all NEMO consortium's institutions

Actions by institutions: these pages contains the other planned developments for the year, as agreed by all consortium members

List of the current sub-pages:

2016 SHARED ACTIONS:

AGRIF, Configuration Manager, Simplification, Robustness and test cases, Wave coupling, GMD

2016 other actions by institution:

CMCC-NEMO team https://forge.ipsl.jussieu.fr/nemo/wiki/2016WP/CMCC_2016
CNRS-INSU NEMO team https://forge.ipsl.jussieu.fr/nemo/wiki/2016WP/CNRS_2016
INGV-NEMO team https://forge.ipsl.jussieu.fr/nemo/wiki/2016WP/INGV_2016
MERCATOR-NEMO team https://forge.ipsl.jussieu.fr/nemo/wiki/2016WP/MERCATOR_2016
Met Office-NEMO team https://forge.ipsl.jussieu.fr/nemo/wiki/2016WP/Met_Office_2016
NOC-NEMO team https://forge.ipsl.jussieu.fr/nemo/wiki/2016WP/NOC_2016

2017WP

Workplan content

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

      Tickets
      'Type: Task'
      'Milestone: 2017 WP'

      Ticket Summary Owner Workplan status Comments
      #1458 AGRIF-1 / Met Office-7 - Vertical grid refinement using AGRIF (2015) timgraham
      #1965 AGRIF3 Jerome-vvl jchanut
      #1896 CONFIGMAN-1/SIREN nemo
      #1897 CONFIGMAN-2/SIREN nemo
      #1898 CONFIGMAN-3/SIREN nemo
      #1814 ENHANCE-01 New nemo-ocean.eu website nemo
      #1815 ENHANCE-03 New Users area in Trac nicolasmartin
      #1911 ENHANCE-05 — RK-3 time stepping gm
      #1926 ENHANCE14 dev_r8329_ENHANCE14_SAL branch development jchanut
      #1918 ENHANCE-17 — Multi-Column Ocean scheme (MCO) gm
      #1959 ENHANCE-4_Jerome_freesurface jchanut
      #1644 Few bugs in Trusting process nicolasmartin
      #1880 HPC-08 — 3D lbc_lnk argument with any size for the 3rd dimension gm
      #1883 HPC-09_Gurvan — ZDF restructuration with reduced number of lbc_lnk call gm
      #1943 HPC-6_Silvia Development of the NEMO hybrid parallel version based on MPI/OpenMP mocavero
      #1881 Met_Office-1 Use XIOS to read single file restart file andmirek
      #1955 NOC-2_JamesH-SCO_ISF development branch
      #1916 ROBUST 10 Unify MPPINI nemo
      #1842 ROBUST-2 enhancement in TEST CASES flavoni
      #1915 ROBUST-8_AndrewC-MPP_no_ghost development branch acc
      #1941 TO DO list for the end of the 2017 merge party nemo
      #1640 Wiki page for Trusting nicolasmartin
      #1962 Write restart file using XIOS andmirek
      #1953 XIOS restart read functionality andmirek

      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.

      Reminders

      • Wikipage name pattern:
        {WG for shared or INSTITUTE for specific actions}-{action number}_{PI(S)}-{keyword(S)}
      • Current WG: AGRIF | CONFIGMAN | ENHANCE | HPC | ROBUST | WAVE

      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.

      Milestone: 2018 WP

      Due in 14 months (2019-01-01T01:00:00+01:00) ; For release-4.0

      2018WP

      Workplan content

      2018 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 2018 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
      (2018WP/AGRIF-*)
      CONFIGMAN
      (2018WP/CONFIGMAN-*)
      Enhancement
      (2018WP/ENHANCE-*)
      HPC
      (2018WP/HPC-*)
      Publication
      (2018WP/PUBLI-*)
      Robustness
      (2018WP/ROBUST-*)
      Sea-Ice
      (2018WP/SEAICE-*)
      Validation
      (2018WP/VALID-*)

      Specific Actions

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

      CMCC actions?
      (2018WP/CMCC-*)
      CNRS actions?
      (2018WP/CNRS-*)
      INGV actions?
      (2018WP/INGV-*)
      Mercator Océan actions?
      (2018WP/Mercator_Ocean-*)
      Met_Office actions?
      (2018WP/Met_Office-*)
      NOC actions?
      (2018WP/NOC-*)

                Overall status

                Tickets
                'Type: Task'
                'Milestone: 2018 WP'

                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.

                Reminders

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

                Ticket fields setting

                • 'Type: Task', 'Milestone: 2018 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.

                Pending issues in the documentation

                Intro

                Model Basics

                * suppress rigid-lid option
                * achieve z* &  s-coordinate description, §2.4 and §2.5
                

                DOM

                * suppress rigid-lid option
                * modify the figure of horizontal indexation : F-point in white circle
                * missing a figure to explain the way the last ocean level thickness is defined in partial step 
                * Add in the  introduction a kind of flowchart in order to give the general structure of the DOM staff
                * Find a place where the description of the T-S and velocity initialisation can be put
                * restart:  explain that the restart staff is distributed in the module....   
                              + explain which variable are required and why...
                

                TRA

                trabbl advective to be added  i.e. §4.5.2, and the associated figure can be improved
                traqsr : modification associated with RGD light penetration (#459)
                

                DYN

                roughly  OK   even if a lot of §  can be improved
                
                * dynspg_ts   :   the averaging period has been changed => add that to the doc and modify the figure
                * suppress rigid-lid option
                

                SBC

                modification associated with RGD light penetration and ocean color (#459)
                

                LBC

                missing description:
                * north fold   §7.2.2
                * mpp   §7.3    only old staff are included
                * flow relaxation scheme  §7.5  together with its introduction in NEMO
                

                LDF

                to be updated 
                

                ZDF

                Pending:
                      new TKE to be introduced           (gurvan's TODO list)
                      TKE2 improvement to be added from the the doc sended by MERCATOR
                      zdftmx : tidal mixing parameterisation to be added (#459)
                
                

                MISC

                * un resolved straits  to be updated
                ...
                

                Appendix

                * Appendix A      OK
                
                * Appendix B      OK
                
                * Appendix C      update the demonstration for the s-coordinate
                
                * Appendix D     Coding rules ...    Urgently revise the naming rule  
                

                Series of various improvements that have not been introduced in the schedule.

                See Misc.Items

                Note: See TracRoadmap for help on using the roadmap.