Fortuna 2.5 User's Guide: Difference between revisions

Line 81: Line 81:
(To use HISTORY.AGCM.rc.tmpl from current build, Type:  Current        )
(To use HISTORY.AGCM.rc.tmpl from current build, Type:  Current        )
-------------------------------------------------------------------------
-------------------------------------------------------------------------
Hit ENTER to use Default Tag/Location: (Fortuna-2_4)
Hit ENTER to use Default Tag/Location: (Fortuna-2_5)
</pre>
</pre>


Line 142: Line 142:
-----
-----
   
   
Build Directory: /discover/nobackup/aeichman/Fortuna-2_4
Build Directory: /discover/nobackup/aeichman/Fortuna-2_5
----------------
----------------
   
   
Line 148: Line 148:
The following executable has been placed in your Experiment Directory:
The following executable has been placed in your Experiment Directory:
----------------------------------------------------------------------
----------------------------------------------------------------------
/discover/nobackup/aeichman/Fortuna-2_4/Linux/bin/GEOSgcm.x
/discover/nobackup/aeichman/Fortuna-2_5/Linux/bin/GEOSgcm.x
   
   
   
   
Line 169: Line 169:
A cleanly completed model run will leave a set of restarts and the corresponding <code>cap_restart</code> in its experiment directory.  Another source is <code>/archive/u/aeichman/restarts</code>.  Restarts are also left during runs in date-labeled tarballs in the <code>restarts</code> directory under the experiment directory before being transferred to the user's <code>/archive</code> space.  You may have to create the <code>cap_restart</code>, which is simply one line of text with the date of the restart files in the format ''YYYYMMDD HHMMSS'' (with a space).  
A cleanly completed model run will leave a set of restarts and the corresponding <code>cap_restart</code> in its experiment directory.  Another source is <code>/archive/u/aeichman/restarts</code>.  Restarts are also left during runs in date-labeled tarballs in the <code>restarts</code> directory under the experiment directory before being transferred to the user's <code>/archive</code> space.  You may have to create the <code>cap_restart</code>, which is simply one line of text with the date of the restart files in the format ''YYYYMMDD HHMMSS'' (with a space).  


Failing the above sources, you can convert restarts from different resolutions and model versions, including MERRA, as described in  [[Regridding Restarts for Fortuna 2.4]].
Failing the above sources, you can convert restarts from different resolutions and model versions, including MERRA, as described in  [[Regridding Restarts for Fortuna 2.5]].