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

1. = 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

*