Changes between Version 15 and Version 16 of WorkingGroups/ConfigurationManager
- Timestamp:
- 2013-02-25T12:03:46+01:00 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WorkingGroups/ConfigurationManager
v15 v16 87 87 * Gauss like - distance weighted function using nearest 9 points with a decorrelation distance r0 proportional to dx*cos(lat(j,i)) 88 88 * Nearest - takes closest point on distance (for use with similar res src and dst grids) 89 90 89 * Then in the vertical 91 90 * Linear … … 99 98 = ''' 4. How MetOffice creates regional configuration ''' = 100 99 1. Hypothesis 101 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. 102 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. 103 100 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. 101 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. 104 102 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 103 * Only handles latitude/longitude grids (with possible rotation). 104 * Does not make use of flexibility of BDY module - only handles regular rectangular boundaries at edge of the domain. 108 105 1. Coordinates 109 An 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 106 An 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. 111 107 1. Bathymetry 112 Bathymetry 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 108 Bathymetry 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. 114 109 1. Boundary condition + Tide 115 An 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. 116 Boundary data is generated using 3D linear interpolation. Tidal harmonic forcing data is interpolated from output from a tidal model. 117 118 110 An 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. 111 Boundary data is generated using 3D linear interpolation. Tidal harmonic forcing data is interpolated from output from a tidal model. 119 112 1. Initial condition 120 Regional 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 113 Regional 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. 122 114 1. Runoff 123 Runoff 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 115 Runoff 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. 125 116 1. Surface forcing 126 117 Surface forcing is derived from Met Office atmosphere model fields and interpolated to model points using bilinear interpolation. … … 144 135 1. define minimum depth; 145 136 1. refine land-sea mask on the base of the coast-line dataset (matlab GUI); The idea is to preserve realistic coast line despite the minimum depth; 146 147 137 1. Initial Condition 148 138 1. required input file: observations, already existing mapped climatology (SeaDataNet, MedAtlas), or parent model results; 149 139 1. In case of sparse observation we do Objective Analysis to map the data into the model grid. in case of already existing mapped data we do a simple linear interpolation; 150 140 1. after the IC file is created we check for vertical stability and correct if necessary; 151 152 141 1. Forcing 153 142 1. surface forcings; No specific tools are used here, just convert grib into netcdf according NEMO needs;
