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/ConfigurationManager (diff) – NEMO

Changes between Version 13 and Version 14 of WorkingGroups/ConfigurationManager


Ignore:
Timestamp:
2013-02-25T10:37:21+01:00 (11 years ago)
Author:
jpaul
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkingGroups/ConfigurationManager

    v13 v14  
    9999= ''' 4. How MetOffice creates regional configuration ''' = 
    100100 1. Hypothesis 
     101Regional 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. 
     102Most 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. 
     103 
    101104 1. Limits 
     105 * Only handles latitude/longitude grids (with possible rotation). 
     106 * Does not make use of flexibility of BDY module - only handles regular rectangular boundaries at edge of the domain. 
     107 
    102108 1. Coordinates 
     109An IDL routine takes the model bathymetry as input (see 4.3) and generates the NEMO coordinates.nc file as well as the grid definition files required by the SCRIP routines. Note that this routine can only handle latitude/longitude grids with possible rotation. 
     110 
    103111 1. Bathymetry 
    104  1. Boundary condition 
     112Bathymetry on the model domain is derived from the GEBCO dataset using a box-averaging algorithm, ie. all data points within a model gridbox are averaged to find the model depth at that point. IDL code. Bathmetry at open boundaries is matched to the bathymetry of the low-resolution model supplying the boundary data. Sometimes hand editing of the bathymetry is performed, eg. to remove nearly-enclosed inlets on the coast. Bathymetry for the North-West Shelf domain is derived from the NOOS 1 nautical mile bathymetry using grid-box averaging. 
     113 
     114 1. Boundary condition + Tide 
     115An IDL routine takes the model coordinates.nc le as input and generates the coordinates.bdy.nc file (definition of boundary in BDY module) as well as the grid definition files required by SCRIP. Note that this routine can only handle regular open boundaries around the edge of a rectangular domain, so doesn't make use of the flexibility of the boundary zone definition in BDY. 
     116Boundary data is generated using 3D linear interpolation. Tidal harmonic forcing data is interpolated from output from a tidal model. 
     117 
     118 
    105119 1. Initial condition 
    106  1. Tide 
     120Regional models are spun up from rest. Initial temperature and salinity fields are either taken from climatology or from a low-resolution FOAM analysis. The temperature and salinity fields are interpolated to the model grid using 3D linear interpolation. 
     121 
    107122 1. Runoff 
     123Runoff is generated from the GRDC climatological dataset using a set of bespoke scripts and fortran code. For each river the data point nearest to the coast is selected and applied to the nearest coastal point in the model. For large rivers the runoff is spread over a number of ocean points. Runoff is applied as a surface flux. 
     124 
    108125 1. Surface forcing 
     126Surface forcing is derived from Met Office atmosphere model fields and interpolated to model points using bilinear interpolation. 
     127 
    109128= ''' 5. How INGV creates regional configuration ''' = 
    110129 1. Hypothesis