GEOS-5 Quick Start: Difference between revisions

Line 64:

where <code>.g5_modules</code> is simply a copy of the <code>g5_modules</code> that you ran earlier before compiling.

Copy the restart (initial condition) and <code>cap_restart</code> ~~(t=t0) files~~ into ''EXPDIR''. Keep the "originals" handy since if the model crashes early in the run it might have renamed them. The model expects restarts to end in "rst" but produces them with the date at time appended to the filename, so you may have to rename them. The <code>cap_restart</code> file is simply one line of text with the format YYYYMMDD HHMMSS. The boundary conditions/forcings are provided by symbolic links created by the run script.

Copy the restart (initial condition) files and associated <code>cap_restart</code> into ''EXPDIR''. Keep the "originals" handy since if the model crashes early in the run it might have renamed them. The model expects restarts to end in "rst" but produces them with the date at time appended to the filename, so you may have to rename them. The <code>cap_restart</code> file is simply one line of text with the date of the restart files in the format YYYYMMDD HHMMSS. The boundary conditions/forcings are provided by symbolic links created by the run script.

The script you submit, <code>gcm_run.j</code>, is in ''HOMEDIR''. It should be ready to go as is, though you may eventually want to tune JOB_SGMT (the number of days per segment, the internal between saving restarts) and NUM_SGMT (the number of segments attempted in a job) to maximize your run time. END_DATE can be changed to your end date, or just left as is. Commenting out the <code>qsub gcm_run.j</code> at the end of the script will stop it, too. Those and the PBS (batch system) parameters at the beginning are all that you will usually want to change in the script.

@@ Line 64: / Line 64: @@
 where <code>.g5_modules</code> is simply a copy of the <code>g5_modules</code> that you ran earlier before compiling.
-Copy the restart (initial condition) and <code>cap_restart</code> (t=t0) files into ''EXPDIR''.   Keep the "originals" handy since if the model crashes early in the run it might have renamed them.  The model expects restarts to end in "rst" but produces them with the date at time appended to the filename, so you may have to rename them.   The <code>cap_restart</code> file is simply one line of text with the format YYYYMMDD HHMMSS.  The boundary conditions/forcings are provided by symbolic links created by the run script.
+Copy the restart (initial condition) files and associated <code>cap_restart</code> into ''EXPDIR''.   Keep the "originals" handy since if the model crashes early in the run it might have renamed them.  The model expects restarts to end in "rst" but produces them with the date at time appended to the filename, so you may have to rename them.   The <code>cap_restart</code> file is simply one line of text with the date of the restart files in the format YYYYMMDD HHMMSS.  The boundary conditions/forcings are provided by symbolic links created by the run script.
 The script you submit, <code>gcm_run.j</code>, is in ''HOMEDIR''.  It should be ready to go as is, though you may eventually want to tune JOB_SGMT (the number of days per segment, the internal between saving restarts) and NUM_SGMT (the number of segments attempted in a job) to maximize your run time.  END_DATE can be changed to your end date, or just left as is.  Commenting out the <code>qsub gcm_run.j</code> at the end of the script will stop it, too.  Those and the PBS (batch system) parameters at the beginning are all that you will usually want to change in the script.