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.
DevelopersCommittee/Agenda/2013-06-18 (diff) – NEMO

Changes between Version 82 and Version 83 of DevelopersCommittee/Agenda/2013-06-18


Ignore:
Timestamp:
2013-06-03T09:47:22+02:00 (11 years ago)
Author:
clevy
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevelopersCommittee/Agenda/2013-06-18

    v82 v83  
    21212:00 – 3:30            '''Discussion on the five white papers and additional contributions''' 
    2222 
    23 3:30 – 4:15            Thematic discussions:[[BR]][[BR]]'''Session 1: NEMO platform: seamless to what extend?''' (Leaders: J. Holt and P. Marsaleix) With ORCA12 (global 1/12°) are we reaching an optimal level? Should we continue moving towards higher resolutions or should we stop there and work in a probabilistic way to quantify errors?[[BR]]In the future, is the NEMO platform expected to be modelling all time and space scales from global to coastal (up to rivers, tide banks, module sedimentary module, etc…) or is there a boundary in small scales (coastal) and associated processes where NEMO should stop, and/or be properly connected to another modelling platform? 
     233:30 – 4:15            Thematic discussions:[[BR]][[BR]]'''Session 1: NEMO platform: seamless to what extend?''' (Leaders: J. Holt and P. Marsaleix) With ORCA12 (global 1/12°) are we reaching an optimal level? Should we continue moving towards higher resolutions or should we stop there and work in a probabilistic way to quantify errors?[[BR]]In the future, is the NEMO platform expected to be modelling all time and space scales from global to coastal (up to rivers, tide banks, module sedimentary module, etc…) or is there a boundary in small scales (coastal) and associated processes where NEMO should stop, and/or be properly connected to another modelling platform?[[BR]]Contours of NEMO in the future (components, diagnostics, data reduction) 
    2424 
    25254:15 - 4:45   Coffee break 
     
    4141'''Session 5: Contours and limits of the assimilation component of NEMO''' (Leader: P. Brasseur & tbd) 
    4242 
    43 '''Session 6: NEMO validation and contours of user support: '''Although  having all possible options working all the time is the NEMO user's  dream, it is not possible. What is needed and where does the System Team  stops? (Leader : P. Oddo & tbd) 
     43'''Session 6: NEMO validation and contours of user support: '''Although  having all possible options working all the time is the NEMO user's  dream, it is not possible. What is needed and where does the System Team  stops? How many reference configurations should be supported by the Systems Team and what should they be? (Leader : P. Oddo & tbd) 
    4444 
    454511:00 – 11:20            Coffee break[[BR]][[BR]]11:20 -12:00 '''           Conclusions “on the fly” '''by a group including CMCC(S. Dobricic), CNRS(tbd), INGV(P. Oddo), Mercator(tbd), Met-Office(tbd), NERC-NOC(tbd):Suggestions of the committee: for the summary of final document, how to build NEMO’s roadmap for the next 10 years?[[BR]]Suggestions to Steering Committee for next steps (writing and discussing the final document)