New URL for NEMO forge!

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.
2020WP – NEMO

2020 Workplan

The NEMO development is planned on a yearly basis relying on the [zenodo:1472458 NEMO Development Strategy document], which designs the long term evolution (5 to 10 years) in both scientific and engineering aspects.

Shared actions

The 2020 workplan is made up of shared actions which are the development priorities for all consortium's institutions.

(nesting tools and zooms)


Air-Sea interactions


(dynamical core)


Physical Processes



(tracers and biogeochemistry)


Data interface, IOM





2020 WP


Add a proposed action in the work plan

At this stage (autumn 2019), we are building the list of possible actions for 2020. The 2020 work plan will be finalised by end of the year, with advice from the Developers Committee and decisions from the Steering committee.
The 2020 workplan must be realistic. Each action must define the 2020 objective only. If the action is expected to take more than one year, it should be explained in the Description section of the associated wiki page (see below).
To add an action in 2020 work plan proposal, you need to create the wiki page (for all actions) and the associated ticket (for 2020 IMMERSE actions only, since those are for sure already).
Once the 2020 workplan will be finalised (after Steering Committee meeting) each action will need its wiki page (action description) and its ticket (following the state of the work).
Adding a proposed action is simple: create a wiki page (eventually a ticket) following the naming conventions, and complete the wiki page information. The following description of each step will look very obvious to experienced developers, and hopefully useful for new comers.

Important: naming convention for actions and their associated wiki page and ticket
The name of an action must follow the convention: "STREAM"_"NUMBER"_"login of PI"_"keyword" , to be used both to name its wiki page and its ticket.

Following this convention, the name of the wiki page must be:"STREAM"_"NUMBER"_"login of PI"_"keyword"

  • "STREAM" = one of the headers of the first table (AGRIF, ASINTER, HPC, KERNEL, PHYPRO, SI3, TOP, DATINT, ENHANCE,VALID, PUBS)
  • "NUMBER" = Choose a number (increment +1 to the last action already listed in your stream)
  • "login of PI" : login of the PI on Trac
  • "keyword" = choose a keyword for this action

1/ Create the wiki page

NewPage(id=WPAction, parent=wiki/2020WP, template=Workplan/Action, placeholder=STREAM-NUM_PI-keywords, button=Create action's wikipage)?

2/ Complete the mandatory fields in the wiki page

  • In the Summary section following fields (= those in bold) must be completed:
    • Action = Name and subject of the action
    • PI(S) Names
    • Digest = one sentence stating motivations and main tasks
    • Dependencies = taksks needing to be completed before this action can start, if any
    • Branch = name of development branch following naming convention (source:/NEMO/branches/{YEAR}/dev_r{REV}_{ACTION_NAME}, to add once preview is completed, e.g. not at this stage
    • Previewer(s)Names
    • Reviewer(s) Names
    • Ticket = number of associated ticket (, to be added once ticket is created, e.g. only for IMMERSE actions for now)
  • Description section (mandatory):

Please complete this section in plain English, readable by all. Description should include:

  • goal of development and the methodology
  • reference documents or publications if relevant
  • precise statement of the objective by end 2020
  • If the action is expected to continue after 2020, some elements on the context
  • a statement on the priority : the action will be qualified as feasible if it is listed with associated commitment of the PI, or desirable meaning if is is hoped to be completed

The other sections of wiki page (implementation, documentation update, preview, tests etc... are expected to be completed as the action work is going on.
Once you've saved the edits of your wiki page, reload the 2020WP page to check that your action (its wiki page) now appears in the first table of the page, under the appropriate stream.

3/ For IMMERSE 2020 actions only (for now): create also the ticket for the action

Error: Failed to load processor rbox
No macro or processor named 'rbox' found
  1. Copy the wikipage's name hereafter to create the ticket:
    owner = PI of the action, priority: high= feasible | normal= desirable
  2. Save the ticket and check it appears in the 2020 work plan page (second table).
  3. Add the ticket number in the wiki page you've created at step 1

See the instructions page for the workflow to implement a development in NEMO.

NEMO Developers in 2020

Name Institution % Position
Guillaume Samson MOI 30 MOI Officer
Chanut Jerome MOI 70
Romain Bourdalle Badie MOI 20
Clement Bricaud MOI 20
Olga Hernandez MOI 50
Andrew Coward NOC 50 NOC Officer
Simon Müller NOC 60
Stefanie Rynders NOC 20
George Nurser NOC 20
Mattia Almansi NOC 30
James Harle NOC 20
Claire Lévy CNRS 100 Project manager
Sebastien Masson SU (part of CNRS contribution) 50 CNRS Officer
Clement Rousset CNRS 50
Gurvan Madec CNRS 50
Christian Ethé CNRS 30
Nicolas Martin SU (part of CNRS contribution) 50
Martin Vancoppenolle CNRS 30
Sibylle Techene CNRS 50
Renaud Person IRD (part of CNRS contribution) 50
Amy Young MetO 50 MetO Officer
Davi Carneiro MetO 50
Daley Calvert MetO 30
Mike Bell MetO 20
Dave Storkey MetO 20
Pierre Mathiot MetO 20
Dan Lea MetO 20
David Ford MetO 20
Enda O'dea MetO 20
Mireck Miroslaw MetO 20
Emma Fiedler MetO 20
Dorotea Iovino CMCC 30 CMCC Officer
Italo Epicoco CMCC 30
Emanuela Clementi CMCC 20
Francesca Mele CMCC 20
Stefania Ciliberti CMCC 20
Tomas Lovato CMCC 20
Massimiliano Drudi CMCC 20
Silvia Mocavero CMCC 20
From other institutions
Laurent Brodeau Ocean Next
Miguel Castrillo BSC

Specific actions

For information, some specific actions are listed as other planned developments coming with additional resources.






          Last modified 19 months ago Last modified on 2020-12-14T11:43:45+01:00