TOC(heading=nemo_ConfigurationManager,nemo_ConfigurationManager/*, depth=1)?

nemo_ConfigurationManager

Last edited Timestamp?

This working group (and wiki pages) are under the responsibility of Julien Paul

The goals of this discussion is to define what will do or not the config manager in the next release of NEMO.

The first step is to define:

• what do we need to create regional configuration
• how each team do it now
  • methods
  • language
  • limits of these methods

Schedule:

1. list method used now (>23 Jan)
2. list idea to solve some limitations (> 03 Feb)
3. Define what will do or not the config manager in the next release of NEMO (> 20 Feb)

The schedule is voluntarily short. First, cause this part should have be done last year. Moreover, if we want to have something reliable to put in the next release of NEMO, we must start to merge tools and write skeleton of the config manager at least in Marsh.

1. = What do we need to create regional configuration =

• coordinates
• bathymetry
• boundary condition
• initial condition
• tide
• runoff
• surface forcing

2. = How Mercator creates regional configuration =

1. Hypothesis
   • orca grid to irca grid
   • odd refinement
   • free licence language
2. Limits
   • can't create domain on north pole or a band of latitude
   • don't create files to used TOP or LIM
   • get data from local space
3. Coordinates
   • extraction of the domain from an already existing coordinates file (Mercator Fortran code). Note that we keep boundary on U,V point.
4. Bathymetry
   • extraction of the domain from an already existing bathymetry file (Mercator Fortran code).
   • merged bathymetry at boundary (~1°) with weighted function (Mercator Fortran code)
5. Boundary condition
   • extrapolation of the above system output (Mercator Fortran code)
     • horizontally (first): distance weighted function using nearest 9 points
     • vertically: takes value of the upper point
   • interpolation to refine grid (T,S,U,V,SSH) (Mercator Fortran code)
     • horizontally: bilinear or bicubic
   • extraction at boundaries (Mercator Fortran code)
   • ouput in OBC form
   • before run NEMO, concatenated files over the period (nco)
6. Initial condition
   • from restart file (netcdf or dimg) or from a "standard" output (Mercator fortran code, nco):
     • extrapolation:
       • horizontally (first): distance weighted function using nearest 9 points
       • vertically: takes value of the upper point
     • interpolation to refine grid (T,S,U,V,SSH):
       • horizontally: bilinear or bicubic
7. Tide

*