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.

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 2020WP/DATINT-*	Enhancements 2020WP/ENHANCE-*	Publications 2020WP/PUB-*	Validation 2020WP/VALID-*
AGRIF-01_mathiot_multigrid_load_balancing AGRIF-02_ girrmann_HPC_performances AGRIF-03_jchanut_vert_coord_interp AGRIF-04_jchanut_tstepping AGRIF-05_rblod_CMEMS	ASINTER-01_ohernandez_traqsr_5bands ASINTER-02_emanuelaclementi_Waves ASINTER-03_laurent_bulk_and_wave ASINTER-04_laurent_bulk_ice ASINTER-05_Masson_CurrentFeedback ASINTER-06_gsamson_ABL_improvement	HPC-01_daley_GPU HPC-02_Daley_Tiling HPC-03_smasson_no_halo_in_input_output HPC-04_mcastril_Mixed_Precision_implementation HPC-05_mcastril_MPI_optimization HPC-06_andmirek_TextOutput HPC-07_mocavero_mpi3 HPC-08_epico_Extra_Halo HPC-09_epico_Loop_fusion HPC-10_mcastril_HPDAonlineDiagGPU	KERNEL-01_Amy_Mike_newHPGschemes KERNEL-02_Coward_DoLoopMacros_part1 KERNEL-03_Storkey_Coward_RK3_stage2 KERNEL-04_Storkey_Coward_RK3_stage3 KERNEL-05_jchanut_ztilde KERNEL-06_techene_better_e3_management KERNEL-07_Gurvan_ShallowWater KERNEL-08_techene_gm_HPG_SPG	PHYPRO-01_agn_OSMOSIS_science PHYPRO-03_jchanut_IWdrag	SI3-01_stefryn_EAP_rheology SI3-02_dcarneir_OBSOP_si_thickness SI3-03_VP_rheology SI3-04_lagrangian_drifters	TOP-01_rlod_Antarctic_ice_Sheet_Fe_Source TOP-02_rlod_SeaIce_Fe_Source TOP-03_cbricaud_CRS TOP-04_lovato_IMMERSE_BGC_interface TOP-05_Ethe_Agrif TOP-06_emalod_OASIS_interface_between_TOP_and_NEMO		ENHANCE-01_davestorkey_fix_3D_momentum_trends ENHANCE-02_daley_Kara_mld ENHANCE-03_djlea_OBSOP_climato_on_obs ENHANCE-04_dford_OBSOP_BGC ENHANCE-05_mathiot_REBUILD ENHANCE-06_JMMP_ICB ENHANCE-07_METO_precip_over_icesheet_cpl ENHANCE-08_davestorkey_fix_2D_vorticity_trends ENHANCE-09_rbourdal_massfluxconvection ENHANCE-10_acc_fix_traqsr ENHANCE-11_smueller_DIAMLR ENHANCE-12_acc_clean_WAD ENHANCE-13_gsamson_ABL_TOOLS ENHANCE-14_smueller_OSMOSIS_streamlining	PUB-01_cbricaud_crs PUB-02_Ethe_TOP_DOC PUB-03_NDS_CHAPTER PUB-05_SI3_documentation	VALID-01_ayoung_SETTE VALID-02_mireck_SAS VALID-03_deazer_AMM15_evaluation VALID-04_storkey_ORCA_evaluation VALID-05_mathiot_debug VALID-06_METO_cpl_interface VALID-07_smueller_unit_testing VALID-08_gsamson_ORCA-ABL-BLK VALID-09_cbricaud_ORCA36 VALID-10_Ethe_TOP_OFF VALID-11_clevy_OASIS_TESTCASE VALID-12_clevy_Trusting_ContinuousIntegration

Follow-up

2020 WP

IMMERSE 2020

0% Total number of tickets: 0 - closed: 0 - active: 0 Ticket Summary Owner No tickets found

100% Total number of tickets: 15 - closed: 15 - active: 0 Ticket Summary Owner #2222 AGRIF-03_jchanut_vert_coord_interp jamesharle #2018 AGRIF-04_jchanut_tstepping jchanut #2155 ASINTER-02_Clementi_wave-mixing emanuelaclementi #2339 ASINTER-02_emanuelaclementi_Waves systeam #2369 ASINTER-04_laurent_bulk_ice laurent #2362 ENHANCE-13_gsamson_ABL_TOOLS gsamson #2365 HPC-02_Daley_Tiling hadcv #2367 HPC-09_epico_Loop_fusion epico #2480 KERNEL-01_Amy_Mike_newHPGschemes ayoung #2356 KERNEL-02_Coward_Do Loop Macros_part1 acc #2354 KERNEL-03_Storkey_Coward_RK3_stage2 acc #2355 KERNEL-03_Storkey_Coward_RK3_stage3 davestorkey #2126 KERNEL-05_jchanut_ztilde jchanut #2352 PHYPRO-01_agn_OSMOSIS_science agn #2351 SI3-01_stefryn_EAP_rheology stefryn

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

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. Click hereafter to create the ticket: ticket for workplan action . Do not change the ticket type, set to "TASK", since it defines the content of the template.
   
2. The following fields are mandatory :
   • Summary = name of the ticket, same as the action name of wiki page = "STREAM"_"NUMBER"_"login of PI"_"keyword"
   • Description: complete the proposed link to the wiki page since you've already wrote it there
   • Select milestone (2020 workplan or 2020 IMMERSE)
   • Select owner = PI of the action
   • Select priority (high= feasible, normal= desirable)
   • Select component
3. Save the ticket and check it appears in the 2020 work plan page (second table).
4. 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
...	...	...	...
...	...	...	...
...	...	...	...
...	...	...	...

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-*
			UKMO-01_Bell_OOPS_JEDI_investigations