New URL for NEMO forge!   http://forge.nemo-ocean.eu

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.
WorkingGroups/DataAssimilation (diff) – NEMO

Changes between Version 5 and Version 6 of WorkingGroups/DataAssimilation


Ignore:
Timestamp:
2017-04-27T21:43:52+02:00 (7 years ago)
Author:
nicolasmartin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkingGroups/DataAssimilation

    v5 v6  
    1 [[TOC(heading=nemo_assim,nemo_assim/*, depth=1)]] 
     1[[PageOutline()]] 
    22 
    3 = '''nemo_assim''' = 
    4 Working group leader: Eric Blayo.[[BR]] In charge of these wiki pages: Dan Lea and Kristian Mogensen[[BR]] 
     3= '''Assim WG''' 
     4 
     5Last edition: '''[[Wikinfo(changed_ts)]]''' by '''[[Wikinfo(changed_by)]]''' 
     6 
     7Working group leader: Eric Blayo.[[BR]] In charge of these wiki pages: Dan Lea and Kristian Mogensen 
    58 
    69---- 
     10 
    711== Members of the Working group: == 
    812 * M. Balmaseda (ECMWF) 
     
    2832 
    2933---- 
    30 == Objectives: == 
     34 
     35== Objectives: 
    3136Definition of several priorities and to the development of several bricks of a NEMO assimilation component 
    3237 
    33 == Agenda: == 
     38== Agenda: 
    3439See annual reports in attached documents: 
    35  
    36  * Report on the first NEMO-Assim meeting - June 2009 
    37  * Report on the 2nd NEMO-Assim meeting - January 2011 
    38  * Report on the 3rd NEMO-Assim meeting - November 2012 
    39  * Report on the 4th NEMO-Assim meeting - November 2015 
     40 * [attachment:wiki:WorkingGroups/nemo_assim:Report-1st-NEMO-ASSIM-meeting.pdf Report on the first NEMO-Assim meeting] - June 2009 
     41 * [attachment:wiki:WorkingGroups/nemo_assim:Report-2nd-NEMO-ASSIM-meeting.pdf Report on the 2nd NEMO-Assim meeting] - January 2011 
     42 * [attachment:wiki:WorkingGroups/nemo_assim:Report-3rd-NEMO-ASSIM-meeting.pdf Report on the 3rd NEMO-Assim meeting] - November 2012 
     43 * [attachment:wiki:WorkingGroups/nemo_assim:4th_NEMO-ASSIM_report.pdf Report on the 4th NEMO-Assim meeting] - November 2015 
    4044 
    4145---- 
    42 == Report for the 2016 Working Plan == 
    43 The NEMO-ASSIM group was created with the aim of sharing scientific and technical expertise about Data Assimilation (DA) with NEMO, and to identify priorities for developing NEMO components required to easily interface the model code and various DA systems. [[BR]][[BR]]Originally, the NEMO-ASSIM membership was established on the basis of contributions from members representing various institutes actively involved in DA systems based on NEMO. A first report (Bell et al, 2009) outlined the scope of the mission of the working group. A report on first achievements was published in 2012 (Bouttier et al., 2012), and a generic concept for the NEMO-ASSIM built-in, interface and external components was proposed from the perspective of long-term developments. [[BR]][[BR]]Following advices from the NEMO-ASSIM group, three components were implemented into NEMO: the observation operator OBS, the increment application operator (ASM) and the linear tangent and adjoint models (TAM). This year, a reference configuration for DA, called SEABASS, will be set up to demonstrate how these tools work and to help new users to take in hand the DA interfaces. [[BR]][[BR]]Briefly speaking, considering the progress made during the past 5 years, we would like to give a new impetus to the NEMO-ASSIM working group in order to:[[BR]][[BR]]- Consolidate the concept of NEMO-ASSIM as outlined here above,[[BR]]- Gather broader scientific and technical expertise based on a larger variety of DA systems that could be interfaced with NEMO[[BR]]- Recommend and implement essential developments to be integrated in the NEMO system core that will facilitate interfaces between NEMO and a number of DA systems in use today.[[BR]][[BR]]Several implementations of DA with NEMO have been performed in the past few years, which are not currently represented in the NEMO-ASSIM working group.  This was confirmed during the last NEMO-ASSIM meeting which has taken place in January 2015.[[BR]][[BR]]In that context, we plan to set up this year a new NEMO-ASSIM working group, smaller than before (around ten persons) with clear objectives which will be written in a terms of Reference document that will be diffused in the next weeks. This group will communicate development recommendations to the NEMO community each year, following the NEMO development agenda.[[BR]][[BR]]In 2015, the nemo_v3_6_STABLE version has been released, focused on the CMIP6 needs. The next version of NEMO is underway now, and will include a major “simplification and robustness” work. [[BR]][[BR]]On our working group side, the new impetus announced here will allow us to set up recommandations and actions for data assimilation in this next NEMO release.[[BR]]The aim for 2016 will be to discuss and build actively these recommandations and list of actions, but no development action for this year. 
     46 
     47== Report for the 2016 Working Plan 
     48The NEMO-ASSIM group was created with the aim of sharing scientific and technical expertise about Data Assimilation (DA) with NEMO, and to identify priorities for developing NEMO components required to easily interface the model code and various DA systems. 
     49 
     50Originally, the NEMO-ASSIM membership was established on the basis of contributions from members representing various institutes actively involved in DA systems based on NEMO. A first report (Bell et al, 2009) outlined the scope of the mission of the working group. A report on first achievements was published in 2012 (Bouttier et al., 2012), and a generic concept for the NEMO-ASSIM built-in, interface and external components was proposed from the perspective of long-term developments. 
     51 
     52Following advices from the NEMO-ASSIM group, three components were implemented into NEMO: the observation operator OBS, the increment application operator (ASM) and the linear tangent and adjoint models (TAM). This year, a reference configuration for DA, called SEABASS, will be set up to demonstrate how these tools work and to help new users to take in hand the DA interfaces. 
     53 
     54Briefly speaking, considering the progress made during the past 5 years, we would like to give a new impetus to the NEMO-ASSIM working group in order to: 
     55- Consolidate the concept of NEMO-ASSIM as outlined here above, 
     56- Gather broader scientific and technical expertise based on a larger variety of DA systems that could be interfaced with NEMO 
     57- Recommend and implement essential developments to be integrated in the NEMO system core that will facilitate interfaces between NEMO and a number of DA systems in use today. 
     58 
     59Several implementations of DA with NEMO have been performed in the past few years, which are not currently represented in the NEMO-ASSIM working group.  This was confirmed during the last NEMO-ASSIM meeting which has taken place in January 2015. 
     60 
     61In that context, we plan to set up this year a new NEMO-ASSIM working group, smaller than before (around ten persons) with clear objectives which will be written in a terms of Reference document that will be diffused in the next weeks. This group will communicate development recommendations to the NEMO community each year, following the NEMO development agenda. 
     62 
     63In 2015, the nemo_v3_6_STABLE version has been released, focused on the CMIP6 needs. The next version of NEMO is underway now, and will include a major “simplification and robustness” work. 
     64 
     65On our working group side, the new impetus announced here will allow us to set up recommendations and actions for data assimilation in this next NEMO release.[[BR]] 
     66The aim for 2016 will be to discuss and build actively these recommendations and list of actions, but no development action for this year. 
    4467 
    4568However, given the major "simplification and robustness" work which will occur this year, this new working group could review the major code modifications and their impact on the existing or potential data assimilation components. This task could be done by identified people from the new working group members.