GEOS-5

Regridding restarts for Fortuna 2.0: Difference between revisions

← Older edit
 
(23 intermediate revisions by the same user not shown)
Line 1: Line 1:
Here are the basic instructions on how to regrid restarts.
Here are basic instructions on how to regrid restarts, based on a README by Larry Takacs.
 
== Where to get MERRA Restarts ==
 
MERRA restarts are available on the NCCS discover cluster under the following directories:
 
/archive/g_proj5/production/GEOSdas-2_1_4/d5_merra_jan79/rs/
/archive/g_proj5/production/GEOSdas-2_1_4/d5_merra_jan89/rs/
/archive/g_proj5/production/GEOSdas-2_1_4/d5_merra_jan98/rs/
 
Restarts are in subdirectories according to their respective year and month.  The are in the form (as an example) <code>d5_merra_jan79.catch_internal_rst.19910128_21z.bin</code>, which you would otherwise know as <code>catch_internal_rst</code> (with the appropriate <code>cap_restart</code>).  MERRA restart filenames need to be changed to the latter, "entropic" name for the regridding programs.


== Required Restarts ==
== Required Restarts ==
Line 5: Line 15:
The key restarts to modify are:
The key restarts to modify are:


Required Upper-Air Related Restarts:
Required upper-air related restarts:
*fvcore_internal_rst
*<code>fvcore_internal_rst</code>
*moist_internal_rst
*<code>moist_internal_rst</code>
 
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):
Required land-surface related restarts:
*pchem_internal_rst
*<code>catch_internal_rst</code>
*gocart_internal_rst
*<code>vegdyn_internal_rst</code>
*<code>landice_internal_rst</code>
*<code>lake_internal_rst</code>
*<code>saltwater_internal_rst</code>


For DAS-Runs, you may also interpolate:
Optional upper-air related restarts (if you have them):
*agcm_import_rst
*<code>pchem_internal_rst</code>
*<code>gocart_internal_rst</code>


For DAS runs, you may also interpolate:
*<code>agcm_import_rst</code>


==Regridding Upper-Air Related Restarts==
==Regridding Upper-Air Related Restarts==
Line 68: Line 77:
to 1x1.25-deg, you have:
to 1x1.25-deg, you have:


<pre>
rs_hinterp_$ARCH.x -dyn      fvcore_internal_rst
rs_hinterp_$ARCH.x -dyn      fvcore_internal_rst
                     -moist    moist_internal_rst
                     -moist    moist_internal_rst
Line 76: Line 86:
                     -jm      181
                     -jm      181


where
</pre>


TOPO_OLD is linked to:
where <code>TOPO_OLD</code> is linked to:
/discover/nobackup/dkokron/geos5/bcs/GEOSagcm-Eros-beta7p8/DC/144x91/topo_DYN_ave_144x91_DC.data


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


TOPO_NEW is linked to:
and <code>TOPO_NEW</code> is linked to:
/discover/nobackup/dkokron/geos5/bcs/GEOSagcm-Eros-beta7p8/DC/288x181/topo_DYN_ave_288x181_DC.data
 
/discover/nobackup/dkokron/geos5/bcs/GEOSagcm-Eros-beta7p8/DC/288x181/topo_DYN_ave_288x181_DC.data




Line 90: Line 100:
This will produce:
This will produce:


fvcore_internal_rst.0288x0181
fvcore_internal_rst.0288x0181
moist_internal_rst.0288x0181
moist_internal_rst.0288x0181
pchem_internal_rst.0288x0181
pchem_internal_rst.0288x0181
gocart_internal_rst.0288x0181
gocart_internal_rst.0288x0181
 
These are the finished restarts.  They will have to be renamed -- truncated after <code>rst</code> -- in order to be recognized by the model in its standard configuration.
 
Note that even if you have no restarts that fall under the <code>-other</code> option, you still have to include that option (with nothing after it) in the command.


==Regridding Land-Surface Related Restarts==
==Regridding Land-Surface Related Restarts==
Line 100: Line 114:


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


At this point it is best to update your directory to the HEAD of CVS to
At this point it is best to update your directory to the HEAD of CVS to
Line 107: Line 121:
  cvs upd -A
  cvs upd -A


Under the mk_restarts directory you have the directories:
Under the <code>mk_restarts</code> directory you have the directories:


  InData
  InData
Line 114: Line 128:
The basic idea is:
The basic idea is:
#Put your existing land-related restarts in the <code>InData</code> directory
#Put your existing land-related restarts in the <code>InData</code> directory
#Put your existing tile file in the <code>InData</code> directory
#Put the appropriate tile file for your current resolution in the <code>InData</code> directory
#Put your target resolution tile file in the <code>OutData</code> directory
#Put your target resolution tile file in the <code>OutData</code> directory
Where to find the appropriate tile file depends on the Fortuna versions you are regridding ''from'' and ''to'', and is detailed below.


Run  <code>mk_Restarts</code>
Run  <code>mk_Restarts</code>


Your regridded restarts will be produced in the <code>OutData</code> directory.
Your regridded restarts will be produced in the <code>OutData</code> directory.


Caveats:
Finally, ''in the case of Fortuna 2.0'', you will need to run <code>newcatch</code> on the catchment restart file.  Rename <code>catch_internal_rst</code> to <code>catch_internal_rst_old</code>, and then run:
 
../newcatch catch_internal_rst_old catch_internal_rst
 
===Old and New Tile Files===


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


#Converting existing restarts to resolutions: 144x91, 288x181, 540x361, 1080x721 (Old Tile Files)
#Converting existing restarts to resolutions: 144x91, 288x181, 540x361, 1080x721 (old tile files for Fortuna 1.4 and earlier)
#Converting existing restarts to resolutions: 144x91, 288x181, 576x361, 1152x721 (New Tile Files)
#Converting existing restarts to resolutions: 144x91, 288x181, 576x361, 1152x721 (new tile files for Fortuna 1.5 and later)




The Old Tile Files are those files which are currently archived in:
The old tile files 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/144x91/FV_144x91_DC_360x180_DE.til
Line 137: Line 157:
  /discover/nobackup/ltakacs/bcs/Fortuna-1_4/1080x721/FV_1080x721_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:
The new tile files are located in:


  /discover/nobackup/ltakacs/bcs/Fortuna-1_5/144x91/FV_144x91_DC_360x180_DE.til
  /discover/nobackup/ltakacs/bcs/Fortuna-2_0/144x91/FV_144x91_DC_360x180_DE.til
  /discover/nobackup/ltakacs/bcs/Fortuna-1_5/288x181/FV_288x181_DC_360x180_DE.til
  /discover/nobackup/ltakacs/bcs/Fortuna-2_0/288x181/FV_288x181_DC_360x180_DE.til
  /discover/nobackup/ltakacs/bcs/Fortuna-1_5/576x361/FV_576x361_DC_360x180_DE.til
  /discover/nobackup/ltakacs/bcs/Fortuna-2_0/576x361/FV_576x361_DC_360x180_DE.til
  /discover/nobackup/ltakacs/bcs/Fortuna-1_5/1152x721/FV_1152x721_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:
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)
====1) Target tile file is from OLD set (model tags <code>Fortuna-1_4</code> and earlier)====
--------------------------------------------------------------------
Since your target tile file is OLD (and not consistent with the new
Since your target Tile File is OLD (and not consistent with the new
<code>mosaic_veg_typs_fracs</code> data), you have to remove the
mosaic_veg_typs_fracs data), you have to remove the
<code>mosaic_veg_typs_fracs</code> file from the <code>InData</code> direcory (or simply rename
mosaic_veg_typs_fracs file from the InData direcory (or simply rename
it, eg: <code>mosaic_veg_typs_fracs.hold</code>).  In its place you have to copy the
it, eg: mosaic_veg_typs_fracs.hold).  In its place you have to copy the
OLD <code>nirdf.dat</code>, <code>visdf.dat</code>, and <code>lai_grn_clim</code> boundary condition datasets
OLD nirdf.dat, visdf.dat, and lai_grn_clim boundary condition datasets
into the <code>InData</code> directory.  These can be found in the corresponding
into the InData directory.  These can be found in the corresponding
<code>/discover/nobackup/ltakacs/bcs/Fortuna-1_4</code> directories.  Note, the names
/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
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
<code>bcs</code> directory.  Therefore you need to link the old datasets to the
proper names.  For example, regridding FROM the old 540x361 resolution
proper names.  For example, regridding FROM the old 540x361 resolution
(eg. MERRA), you should have:
(eg. MERRA), you should have:


nirdf.dat ->
<code>nirdf.dat ->
/discover/nobackup/ltakacs/bcs/Fortuna-1_4/540x361/nirdf_540x361_DC.dat
/discover/nobackup/ltakacs/bcs/Fortuna-1_4/540x361/nirdf_540x361_DC.dat</code>
 
<code>visdf.dat ->
/discover/nobackup/ltakacs/bcs/Fortuna-1_4/540x361/visdf_540x361_DC.dat</code>
 
<code>lai_grn_clim ->
/discover/nobackup/ltakacs/bcs/Fortuna-1_4/540x361/lai_green_clim_540x361_DC.data</code>
 
====2) Target tile file is from NEW set (model tags <code>Fortuna-1_5</code> and later)====
 
In this case, the target tile files are consistent with the <code>mosaic_veg_typs_fracs</code> dataset which resides in the <code>InData</code> directory.
Therefore you do not have link in the old <code>nirdf.dat</code>, <code>visdf.dat</code>, and
<code>lai_grn_clim</code> datasets.
 
== Bootstrapping for a Complete Set of Restarts ==
 
The above procedure produces all the necessary restart files for the model to run, but others are needed for proper function.  The model can produce them starting from the minimal set created by the regridding procedure; this requires some modification of the <code>AGCM.tmpl</code> file in your experiment home directory (probably under your account home directory). 


visdf.dat ->
In <code>AGCM.tmpl</code> -- you probably want to keep a copy of the default version for normal runs -- and using <code>turb_import_rst</code> as an example, comment out the lines referring to <code>RESTART</code>:
/discover/nobackup/ltakacs/bcs/Fortuna-1_4/540x361/visdf_540x361_DC.dat


lai_grn_clim ->
TURBULENCE_IMPORT_RESTART_FILE:        turb_import_rst
/discover/nobackup/ltakacs/bcs/Fortuna-1_4/540x361/lai_green_clim_540x361_DC.data
TURBULENCE_IMPORT_RESTART_TYPE:        binary
TURBULENCE_IMPORT_CHECKPOINT_FILE:      turb_import_checkpoint
TURBULENCE_IMPORT_CHECKPOINT_TYPE:      binary


#TURBULENCE_IMPORT_RESTART_FILE:        turb_import_rst
#TURBULENCE_IMPORT_RESTART_TYPE:        binary
TURBULENCE_IMPORT_CHECKPOINT_FILE:      turb_import_checkpoint
TURBULENCE_IMPORT_CHECKPOINT_TYPE:      binary


2) Target Tile file is from NEW set (model tags Fortuna-1_5 and later)
Running the model for a model day using this modified <code>AGCM.tmpl</code> will produce a full set of restart files, which can be used with the default model configuration.
----------------------------------------------------------------------
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"