Changes between Version 23 and Version 24 of WorkingGroups/ConfigurationManager

Timestamp:

2014-02-12T11:14:56+01:00 (10 years ago)

Author:

clevy

Comment:

--

WorkingGroups/ConfigurationManager

@@ -8 +8 @@
  * Julien Paul (Mercator)
  * Dave Storkey (Met Office)
- * Srdjan Dobricic(CMCC)
- * James Harles (NOC)
- * Sébastien Masson (CNRS)
- * Luca Giacomelli (INGV)
+ * Paolo Oddo (INGV)
 
 
@@ -54 +51 @@
  * surface forcing
 
-= ''' 2. How Mercator creates regional configuration ''' =
+==  2. How Mercator creates regional configuration  ==
  1. Hypothesis
    * orca grid to irca grid
@@ -95 +92 @@
    * manage inside NEMO, using interpolation on the fly.
 
-= ''' 3. How NOC creates regional configuration ''' =
+== 3. How NOC creates regional configuration ==
  1. Boundary condition : BDY tools
 
@@ -116 +113 @@
  * At present is only coded to use TPXO7.2 inverse tidal model to provide tidal boundary conditions
 
-= ''' 4. How MetOffice creates regional configuration ''' =
+== 4. How MetOffice creates regional configuration ==
  1. Hypothesis Regional models at the Met Oce up to now have been based on a standard latitude/longitude grid, sometimes rotated (ie. north pole of grid not at geographical north pole).   Open boundaries are handled using the NEMO BDY module. The code for generating the grid definition and model input files is a mixture of IDL and Fortran. Most model input files are generated by 3D linear interpolation. Horizontal interpolation weights are calculated using the SCRIP code developed at Los Alamos. Met Office Fortran routines are used to calculate the vertical interpolation weights and perform the interpolation in 3D using the horizontal and vertical interpolation weights. The interpolation routine can handle full 3D interpolation required for eg.  s-coordinate models.  The interpolation routine rotates vector fields where necessary.
  1. Limits
@@ -130 +127 @@
 Surface forcing is derived from Met Office atmosphere model fields and interpolated to model points using bilinear interpolation.
 
-= ''' 5. How INGV creates regional configuration ''' =
+== 5. How INGV creates regional configuration ==
 Most of the steps are done using matlab/f90 codes; We deal only with regional configuration regular configuration, no global. Our procedure is divided into 3 steps: Grid-[wiki:InitialCondition]-Forcing.
 
@@ -150 +147 @@
    1. Lateral open boundary condition (up to now only OBC, simple test with BDY); up to now only ad-hoc scripts; The only common point are the integral constrains we apply. I.E. Preserve transport before and after the interpolation.
 
-= ''' 6. Proposals to solve some limits ''' =
+== 6. Proposals to solve some limits ==
  * to create orca grid all over the globe (north pole, band of latitude. . . ), we could use Gridgen tool which is already in NEMO.
  * to create Bathymetry on this new grid we could use the GEBCO dataset with the OPABAT tool (already in NEMO).
@@ -160 +157 @@
 AM Treguier proposes to add the BMGtools as potential tools. The BMGtools (developped by Ifremer) allow to refine grid, to create bathymetry and to check it. Moreover she proposes to use AGRIF nesting tools, as there is common tasks for both tools. So it will be easiest to maintain codes.
 
-= ''' 7. What the config manager could do, with which file and tool ''' =
+== 7. What the config manager could do, with which file and tool '==
  1. Coordinates
 
@@ -208 +205 @@
 || '''low resolution climatology or analysis''' || interpolation on the fly || fldread || || ||
 
-= ''' 8. config manager demonstrator ''' =
+== 8. config manager demonstrator ==
 I propose to build a demonstrator tool. This demonstrator will not be able to do all tasks listed in part III. However i will try to take it into account, in order to make it easy to plug in those tools.  The demonstrator will allow to create 1/12° regional configuration, using 1/4° global climatology to initialised and forced the new configuration. Bathymetry and grid will be extract from already existing files. I hope do it before this summer, so you could test it before next fall NEMO meeting, and maybe we could add this demonstrator to the next release of NEMO. Then we could add, step by step, other tools to improve the capabilities of the config manager.