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

SharedActions 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-*)
1_Clement-LIM3 2_TimGraham-vertical 3_Jerome-vvl 4_clementB_northfold_eastwest	1-Julien_improvment 2-Julien_tide_OB_forcing 3-Julien_runoff 4_StefaniaCiliberti-BDYModel 5_StefaniaCiliberti-BDYTool	01_Nicolas_NewWebsite 02_Martin-MeltPonds 03_Nicolas_NewUsersEnv 05_Gurvan-RK3 06_Nicolas-Trusting 07_Gurvan-Vertical_Advection 08_AndrewC-Wetting_and_drying 09_Gurvan-Bulk_improvements 11_GuillaumeR_QuickestAdv 12_Romain-massfluxconvection 13_GuillaumeS_dragairice 14_Jerome_SAL 15_Clement_LIM3adv 16_Clement_ICEMODEL 17_Gurvan_MCO	01_Miguel_Mondher_GatherComm 02_TimGraham_allocate 03_SilviaMocavero_globcomm 04_SilviaMocavero_singlecoreperf 05_DaleyCalvert_LBCLNK 06_SilviaMocavero_hybrid 07_SilviaMocavero_mpi3 08_Gurvan_Unspecified_jpk 09_Gurvan-ZDF	01_PierreAntoine-SEABASSTestCase 02_Simona-TestCases 03_Clement_CRS 04-Martin_Clem-LIM3_DOC 05_Christian-TOPDoc 06_Simona-UserDefMod 07_Christian-PISCESRevisit 08_AndrewC-MPP_no_ghost 09_Tim_Graham_CMIP6doc 10_Tomas_Unify_MPPINI 11_Simona-DocUserdef 12_SystemTeam-TrunkValidation 13_Martin_v36_CMIP6_ice_diagnostics 14_Dave_Storkey-Closed_Seas_rewrite	1_Drudi_Improvements 2_Clementi_add_coupling

Specific Actions

SpecificActions 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-*)
	14_Merino-ICB 1_Martin-LIM3PTRA	1_Mattia_Test_Mediterranean		1_MattMartin_avgoperator 1_Mirek_XIOSread	1_Nurser-OSMOSIS 2_JamesH-SCO_ISF

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.

NewPage(id=WPAction, parent=wiki/2017WP, template=WorkPlanAction, placeholder=Wikipage name, button=Create action's wikipage)? Reminders Wikipage name pattern: {WG for shared actions or INSTITUTE for specific actions}-{action number}_{PI(S)}-{keyword(S)} Current WG: AGRIF | CONFIGMAN? | ENHANCE | HPC? | ROBUST? | WAVE?

Ticket fields setting 'Type': 'Development' 'Milestone' to current yearly WP '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.