Regridding restarts for Fortuna 2.1: Difference between revisions
| (7 intermediate revisions by the same user not shown) | |||
| Line 43: | Line 43: | ||
Note: if the grid dimensions are the same SOME restarts from earlier model versions may be used , while other may not. | Note: if the grid dimensions are the same SOME restarts from earlier model versions may be used , while other may not. | ||
* fvcore_internal_rst and moist_internal_rst may be used directly from earlier versions. | * <code>fvcore_internal_rst</code> and <code>moist_internal_rst</code> may be used directly from earlier versions. | ||
* catch_internal_rst, lake_internal_rst, landice_internal_rst, and saltwater_internal_rst must be re-gridded due to new land surface tile data | * <code>catch_internal_rst</code>, <code>lake_internal_rst</code>, <code>landice_internal_rst</code>, and <code>saltwater_internal_rst</code> must be re-gridded due to new land surface tile data | ||
* All other restarts from earlier versions should be boot-strapped. | * All other restarts from earlier versions should be boot-strapped. | ||
| Line 143: | Line 143: | ||
#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 the appropriate tile file for your current resolution 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 and appropriate <code>clsm</code> directory 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. | Where to find the appropriate tile file depends on the Fortuna versions you are regridding ''from'' and ''to'', and is detailed below. | ||
| Line 150: | Line 150: | ||
Your regridded restarts will be produced in the <code>OutData</code> directory. | Your regridded restarts will be produced in the <code>OutData</code> directory. | ||
===Old and New Tile Files=== | ===Old and New Tile Files=== | ||
| Line 171: | Line 167: | ||
/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 and <code>clsm</code> directories are located in: | ||
/discover/nobackup/ltakacs/bcs/Fortuna-2_1/144x91/FV_144x91_DC_360x180_DE.til | |||
/discover/nobackup/ltakacs/bcs/Fortuna-2_1/288x181/FV_288x181_DC_360x180_DE.til | |||
/discover/nobackup/ltakacs/bcs/Fortuna-2_1/576x361/FV_576x361_DC_360x180_DE.til | |||
/discover/nobackup/ltakacs/bcs/Fortuna-2_1/1152x721/FV_1152x721_DC_360x180_DE.til | |||
(These work for Fortuna 2.1 as well, and are identical to those in <code>/discover/nobackup/ltakacs/bcs/Fortuna-2_1</code> | |||
/discover/nobackup/ltakacs/bcs/Fortuna- | |||
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: | ||
| Line 206: | Line 204: | ||
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</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 | 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. For Fortuna 2.1 you do have to copy or link the <code>clsm</code> directory in directory with the appropriately-dimensioned tile files. | ||
== Bootstrapping for a Complete Set of Restarts == | == 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. | 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.rc</code> file in your experiment home directory (probably under your account home directory). | ||
In <code>AGCM. | In <code>AGCM.rc</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_FILE: turb_import_rst | ||
| Line 224: | Line 222: | ||
TURBULENCE_IMPORT_CHECKPOINT_TYPE: binary | TURBULENCE_IMPORT_CHECKPOINT_TYPE: binary | ||
Running the model for a model day using this modified <code>AGCM. | Running the model for a model day using this modified <code>AGCM.rc</code> will produce a full set of restart files, which can be used with the default model configuration. | ||