Version 33 (modified by clevy, 2 weeks ago) (diff)

2020 Workplan

The NEMO development is planned on a yearly basis relying on the 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.

AGRIF
(nesting tools and zooms)

2020WP/AGRIF-*

Air-Sea interactions
2020WP/ASINTER-*

HPC
2020WP/HPC-*

Kernel
(dynamical core)

2020WP/KERNEL-*

Physical Processes
2020WP/PHYPRO-*

SI3
(sea-ice)

2020WP/SI3-*

TOP
(tracers and biogeochemistry)

2020WP/TOP-*

Data interface, IOM
2020WP/DATAINT-*

Enhancements
2020WP/ENHANCE-*

Publications
2020WP/PUB-*

Validation
2020WP/VALID-*

Follow-up

2020 WP

IMMERSE 2020

Ticket Summary Owner Progress Review MP ready?
#2129 AGRIF-05_rblod_CMEMS rblod Unspecified pending no
#2193 CMCC-03_Clementi_Add Wave Diag emanuelaclementi In progress. Part of this action was included in in previous WP2018 actions (VALID-08_Drudi_Wave_ORCA2, VALID-09_Lovato_TestWave_MedSea) This action will be finalized once the wave interactin processes will be updated during 2020. To be finalized by end 2020. failed no
#2052 ENHANCE-09(2018WP)_rbourdal_massfluxconvection rbourdal first implementation ok; C1D case under evaluation; 3D case to be done pending no
#2350 PHYPRO-03_jchanut_IWdrag jchanut Unspecified pending no
#2023 PUB-01_cbricaud_CRS cbricaud Unspecified failed no
#2191 PUB-03_NDS_CHAPTER vancop Workshop has happened. NDS to be updated in 2020. failed no
#2189 PUB-05_SI3_documentation vancop This task will be ongoing over the duration of IS-ENES3, until 2022. It must be spread among the sea ice working group members during our next meeting in 2020. failed no
#2186 SI3-03_VP_rheology vancop Bound for WP2020 failed no
#2187 SI3-04_lagrangian_drifters vancop Bound for WP2020 failed no

Ticket Summary Owner Progress Review MP ready?
#2336 AGRIF-01_mathiot_multigrid_load_balancing mathiot Unspecified failed no
#2222 AGRIF-03_jchanut_vert_coord_interp jamesharle Development plan for this task is ready. Completion of task AGRIF-01_jchanut_small_jpi_jpj is needed first. pending no
#2018 AGRIF-04_jchanut_tstepping jchanut A new split-explicit free surface integration compliant with AGRIF needs has been designed. The task is however postponed until the new time stepping environment is available. pending no
#2158 ASINTER-03_laurent_bulk_and_wave laurent 0% pending no
#2369 ASINTER-04_laurent_bulk_ice laurent 0% pending no
#2338 DATAINT-01_sciliberti_IMMERSE_Interfaces sciliberti Unspecified failed no
#2362 ENHANCE-13_gsamson_ABL_TOOLS gsamson Unspecified pending no
#2353 ENHANCE-14_smueller_OSMOSIS_streamlining smueller Unspecified failed no
#2365 HPC-02_Daley_Tiling hadcv pending no
#2364 HPC-04_mcastril_Mixed_Precision_implementation mcastril First version ready of the code ready. pending no
#2366 HPC-08_epico_Extra_Halo epico The activity started in 2019 and will be completed in 2020. The management of extra-halo will be completed with the correct management of input/output files pending no
#2367 HPC-09_epico_Loop_fusion epico Started in 2020 pending no
#2368 HPC-10_mcastril_HPDAonlineDiagGPU mcastril As first step, the portability of NEMO diagnostic calculations to GPUs has been analyzed, exploring how to adapt these regions from the current MPI implementation to the CUDA paradigm. A toy model has been created to perform preliminary tests, that were done using the dia_hsb diagnostic. The code itself is executed 50x faster than in a single CPU but the data transfer to and from GPU is the main bottleneck. We are working on the asynchronous strategy in order to hide all communications among GPU/CPU. We also plan to increase the efficiency of the overall solution, by mitigating the impact of the offloaded data and extending our approach to the rest of the diagnostics. pending no
#2356 KERNEL-02_Coward_Do Loop Macros_part1 acc Unspecified failed no
#2354 KERNEL-03_Storkey_Coward_RK3_stage2 acc Unspecified failed no
#2355 KERNEL-03_Storkey_Coward_RK3_stage3 davestorkey Unspecified failed no
#2126 KERNEL-05_jchanut_ztilde jchanut Work has been done but in a 1 year old NEMO version. Review and transfer to the most recent code have to be done. Note that testing of the revised ztilde coordinate is underway in a global 1/4° configuration (Alex Megann). pending no
#2352 PHYPRO-01_agn_OSMOSIS_science agn Unspecified failed no
#2351 SI3-01_stefryn_EAP_rheology stefryn Unspecified failed no
#2150 TOP-02_emalod_OASIS_interface_between_TOP_and_NEMO emalod OASIS interface codes Performance measurement ongoing Milestone to be delivered end of February 2020 failed no
#2363 VALID-08_gsamson_ORCA-ABL-BLK gsamson Unspecified pending no

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: forge.ipsl.jussieu.fr/nemo/wiki/2020WP/"STREAM"_"NUMBER"_"login of PI"_"keyword"
where

  • "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

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

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

In 2020, be careful with the milestone you choose for your ticket!
Should be set either to 2020 WP or IMMERSE 2020

  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.

Staff

Name Institution % Position
Guillaume Samson MOI 30 Officer
Chanut Jerome MOI 70
Romain Bourdalle Badie MOI 20
Clement Bricaud MOI 20
Olga Hernandez MOI 50
Andrew Coward NOC 50 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 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

Specific actions

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

CMCC
2020WP/CMCC-*

CNRS
2020WP/CNRS-*

Mercator_Océan
2020WP/MOI-*

Met_Office
2020WP/UKMO-*

NOC
2020WP/NOC-*