GEOS-5

Regridding restarts for Fortuna 2.0

Revision as of 05:45, 11 February 2010 by Andrew.eichmann (talk | contribs) (→Regridding Upper-Air Related Restarts)

Here are the basic instructions on how to regrid restarts.

Required Restarts

The key restarts to modify are:

Required Upper-Air Related Restarts:

  • fvcore_internal_rst
  • moist_internal_rst

Required Land-Surface Related Restarts:

  • catch_internal_rst
  • vegdyn_internal_rst
  • landice_internal_rst
  • lake_internal_rst
  • saltwater_internal_rst

Optional Upper-Air Related Restarts (if you have them):

  • pchem_internal_rst
  • gocart_internal_rst

For DAS-Runs, you may also interpolate:

  • agcm_import_rst


Regridding Upper-Air Related Restarts

Within your build, go to the directory: 

 src/GMAO_Shared/GEOS_Util/post

Here you will find the files:

  • rs_hinterp (script to compile the Fortran)
  • rs_hinterp.F (Fortran source to regrid)

By running rs_hinterp, it should produce the executable: 

rs_hinterp_Linux.x

Running rs_hinterp_Linux.x shows the usage: 

> rs_hinterp_Linux.x
Usage:

rs_hinterp_$ARCH.x -dyn      DYNRST
                   -moist    MOISTRST
                   -other    OtherRST1 OtherRST2 OtherRST3 ...
                   -topo_old TOPO_OLD
                   -topo_new TOPO_NEW
                   -im       IM_OUT
                   -jm       JM_OUT

where:

  -dyn         DYNRST:  Filename for DYNAMICS_INTERNAL_RESTART
  -moist     MOISTRST:  Filename for    MOIST_INTERNAL_RESTART
  -other     OtherRST:  Filename for Other Flat Binary_RESTART
  -topo_old  TOPO_OLD:  Filename for OLD Topography (associated with INPUT  resolution)
  -topo_new  TOPO_NEW:  Filename for NEW Topography (associated with OUTPUT resolution)
  -im          IM_OUT:  IM Dimension for Output
  -jm          JM_OUT:  JM Dimension for Output


So, as an example, to regrid from an existing 2x2.5-deg set of restarts to 1x1.25-deg, you have: 

rs_hinterp_$ARCH.x -dyn      fvcore_internal_rst
                    -moist    moist_internal_rst
                    -other    pchem_internal_rst  gocart_internal_rst
                    -topo_old TOPO_OLD
                    -topo_new TOPO_NEW
                    -im       288
                    -jm       181

where TOPO_OLD is linked to: 

/discover/nobackup/dkokron/geos5/bcs/GEOSagcm-Eros-beta7p8/DC/144x91/topo_DYN_ave_144x91_DC.data

and TOPO_NEW is linked to: 

/discover/nobackup/dkokron/geos5/bcs/GEOSagcm-Eros-beta7p8/DC/288x181/topo_DYN_ave_288x181_DC.data


This will produce: 

fvcore_internal_rst.0288x0181
moist_internal_rst.0288x0181
pchem_internal_rst.0288x0181
gocart_internal_rst.0288x0181

These are the finished restarts. They will have to be renamed -- truncated after rst -- in order to be recognized by the model in its standard configuration.

Regridding Land-Surface Related Restarts

Within your build, go to: 

src/GEOSgcs_GridComp/GEOSgcm_GridComp/GEOSagcm_GridComp/GEOSphysics_GridComp/ ...
<path continued> GEOSsurface_GridComp/GEOSland_GridComp/GEOScatch_GridComp/mk_restarts

At this point it is best to update your directory to the HEAD of CVS to be sure you have the latest datasets: 

cvs upd -A

Under the mk_restarts directory you have the directories: 

InData
OutData

The basic idea is:

  1. Put your existing land-related restarts in the InData directory
  2. Put your existing tile file in the InData directory
  3. Put your target resolution tile file in the OutData directory

Run mk_Restarts

Your regridded restarts will be produced in the OutData directory.

Caveats:

There are two possible scenarios for regridding land-surface related restarts:

  1. Converting existing restarts to resolutions: 144x91, 288x181, 540x361, 1080x721 (Old Tile Files)
  2. Converting existing restarts to resolutions: 144x91, 288x181, 576x361, 1152x721 (New Tile Files)


The Old Tile Files are those files which are currently archived in: 

/discover/nobackup/ltakacs/bcs/Fortuna-1_4/144x91/FV_144x91_DC_360x180_DE.til
/discover/nobackup/ltakacs/bcs/Fortuna-1_4/288x181/FV_288x181_DC_360x180_DE.til
/discover/nobackup/ltakacs/bcs/Fortuna-1_4/540x361/FV_540x361_DC_360x180_DE.til
/discover/nobackup/ltakacs/bcs/Fortuna-1_4/1080x721/FV_1080x721_DC_360x180_DE.til

The New Tile Files are located in: 

/discover/nobackup/ltakacs/bcs/Fortuna-2_0/144x91/FV_144x91_DC_360x180_DE.til
/discover/nobackup/ltakacs/bcs/Fortuna-2_0/288x181/FV_288x181_DC_360x180_DE.til
/discover/nobackup/ltakacs/bcs/Fortuna-2_0/576x361/FV_576x361_DC_360x180_DE.til
/discover/nobackup/ltakacs/bcs/Fortuna-2_0/1152x721/FV_1152x721_DC_360x180_DE.til

Depending on which Tile file you are regridding to, there are two procedures:

1) Target Tile file is from OLD set (model tags Fortuna-1_4 and earlier)

Since your target Tile File is OLD (and not consistent with the new mosaic_veg_typs_fracs data), you have to remove the mosaic_veg_typs_fracs file from the InData direcory (or simply rename it, eg: mosaic_veg_typs_fracs.hold). In its place you have to copy the OLD nirdf.dat, visdf.dat, and lai_grn_clim boundary condition datasets into the InData directory. These can be found in the corresponding /discover/nobackup/ltakacs/bcs/Fortuna-1_4 directories. Note, the names that the Fortran program is looking for are not the same names in our bcs directory. Therefore you need to link the old datasets to the proper names. For example, regridding FROM the old 540x361 resolution (eg. MERRA), you should have:

nirdf.dat -> /discover/nobackup/ltakacs/bcs/Fortuna-1_4/540x361/nirdf_540x361_DC.dat

visdf.dat -> /discover/nobackup/ltakacs/bcs/Fortuna-1_4/540x361/visdf_540x361_DC.dat

lai_grn_clim -> /discover/nobackup/ltakacs/bcs/Fortuna-1_4/540x361/lai_green_clim_540x361_DC.data


2) Target Tile file is from NEW set (model tags Fortuna-1_5 and later)

In this case, the target TILE files are consistent with the mosaic_veg_typs_fracs dataset which resides in the InData directory. Therefore you do not have link in the old nirdf.dat, visdf.dat, and lai_grn_clim datasets.

Retrieved from "https://geos5.org/wiki/index.php?title=Regridding_restarts_for_Fortuna_2.0&oldid=388"