GEOS-5

Regridding restarts for Fortuna 2.0: Difference between revisions

← Older editNewer edit →
Line 102: Line 102:


  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 128: Line 128:
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 139: Line 139:
  /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-2_0/144x91/FV_144x91_DC_360x180_DE.til
  /discover/nobackup/ltakacs/bcs/Fortuna-2_0/144x91/FV_144x91_DC_360x180_DE.til
Line 146: Line 146:
  /discover/nobackup/ltakacs/bcs/Fortuna-2_0/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 Fortuna-1_4 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
mosaic_veg_typs_fracs data), you have to remove the
<code>mosaic_veg_typs_fracs</code> data), you have to remove the
mosaic_veg_typs_fracs file from the InData direcory (or simply rename
<code>mosaic_veg_typs_fracs</code> file from the <code>InData</code> direcory (or simply rename
it, eg: mosaic_veg_typs_fracs.hold).  In its place you have to copy the
it, eg: <code>mosaic_veg_typs_fracs.hold</code>).  In its place you have to copy the
OLD nirdf.dat, visdf.dat, and lai_grn_clim boundary condition datasets
OLD <code>nirdf.dat</code>, <code>visdf.dat</code>, and <code>lai_grn_clim</code> boundary condition datasets
into the InData directory.  These can be found in the corresponding
into the <code>InData</code> directory.  These can be found in the corresponding
/discover/nobackup/ltakacs/bcs/Fortuna-1_4 directories.  Note, the names
<code>/discover/nobackup/ltakacs/bcs/Fortuna-1_4</code> 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>


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


lai_grn_clim ->
<code>lai_grn_clim ->
/discover/nobackup/ltakacs/bcs/Fortuna-1_4/540x361/lai_green_clim_540x361_DC.data
/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 Fortuna-1_5 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
In this case, the target TILE files are consistent with the
mosaic_veg_typs_fracs dataset which resides in the InData directory.
<code>mosaic_veg_typs_fracs dataset</code> which resides in the <code>InData</code> directory.
Therefore you do not have link in the old nirdf.dat, visdf.dat, and
Therefore you do not have link in the old <code>nirdf.dat</code>, <code>visdf.dat</code>, and
lai_grn_clim datasets.
<code>lai_grn_clim</code> datasets.
Retrieved from "https://geos5.org/wiki/index.php?title=Regridding_restarts_for_Fortuna_2.0"