GEOS-5

Regridding restarts for Fortuna 2.0: Difference between revisions

← Older edit
 
(14 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 96: Line 106:


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.
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 123: Line 135:
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
Line 150: Line 166:
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
<code>mosaic_veg_typs_fracs</code> data), you have to remove the
Line 173: Line 188:
/discover/nobackup/ltakacs/bcs/Fortuna-1_4/540x361/lai_green_clim_540x361_DC.data</code>
/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)====


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 <code>mosaic_veg_typs_fracs</code> dataset which resides in the <code>InData</code> directory.
----------------------------------------------------------------------
In this case, the target TILE files are consistent with the
<code>mosaic_veg_typs_fracs dataset</code> 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
Therefore you do not have link in the old <code>nirdf.dat</code>, <code>visdf.dat</code>, and
<code>lai_grn_clim</code> datasets.
<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). 
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>:
TURBULENCE_IMPORT_RESTART_FILE:        turb_import_rst
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
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.
Retrieved from "https://geos5.org/wiki/index.php?title=Regridding_restarts_for_Fortuna_2.0"