Hello,
Colleagues of mine used 'create_region' to cut out an elliptical domain from the 3km-uniform global grid 'static' file provided at MPAS-Atmosphere mesh downloads, i.e., x1.65536002.static.nc. The 'pts' file used was:
Type: ellipse
Point: 28.5, -67.0
Semi-major-axis: 1800000 # Meters
Semi-minor-axis: 4250000 # Meters
Orientation-angle: 5
I then needed to cut out the same domain from the 'x1.65536002.grid.nc' file, and attempted to do so with the same 'create_region' script and 'pts' file, however a slightly different grid resulted. The 'static.nc' file that was generated had 'nCells = 3014402'. The regional 'grid.nc' file ended up with 'nCells = 3014403', that is, it had one extra grid point. Looking at the differences between the 3km global static.nc and grid.nc files is that the 'latCell' and 'lonCell' variables are 'double' precision in the 'grid.nc' file and 'float' in 'static.nc'. I'm wondering if this is the cause of the mis-matched meshes, i.e., due to differing round-off errors.
-- Mike
Colleagues of mine used 'create_region' to cut out an elliptical domain from the 3km-uniform global grid 'static' file provided at MPAS-Atmosphere mesh downloads, i.e., x1.65536002.static.nc. The 'pts' file used was:
Type: ellipse
Point: 28.5, -67.0
Semi-major-axis: 1800000 # Meters
Semi-minor-axis: 4250000 # Meters
Orientation-angle: 5
I then needed to cut out the same domain from the 'x1.65536002.grid.nc' file, and attempted to do so with the same 'create_region' script and 'pts' file, however a slightly different grid resulted. The 'static.nc' file that was generated had 'nCells = 3014402'. The regional 'grid.nc' file ended up with 'nCells = 3014403', that is, it had one extra grid point. Looking at the differences between the 3km global static.nc and grid.nc files is that the 'latCell' and 'lonCell' variables are 'double' precision in the 'grid.nc' file and 'float' in 'static.nc'. I'm wondering if this is the cause of the mis-matched meshes, i.e., due to differing round-off errors.
-- Mike