Fortuna 2.1 Quick Start: Difference between revisions

Line 81:

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~~. ~~Leave END_DATE alone~~ in Fortuna 2.~~0 -- there is a bug that erroneously resubmits~~ the ~~script after this date~~. ~~You can~~ stop the run by commenting out the <code>qsub $HOMDIR/gcm_run.j</code> at the end of the script, which will prevent the script from being resubmitted. ~~Those and~~ the ~~PBS~~ (~~batch system~~) ~~parameters at~~ the ~~beginning are all that you will usually want~~ to ~~change in the script~~.

The script you submit, <code>gcm_run.j</code>, is in ''HOMEDIR''. It should be ready to go as is. The parameter END_DATE in <code>CAP.rc</code> (previously in <code>gcm_run.j</code>) can be set to the date you want the run to stop -- this works in Fortuna 2.1 where it did not in Fortuna 2.0. Also in Fortuna 2.1, you may edit the <code>.rc</code> files directly instead of template (<code>.tmpl</code>). An alternative way to stop the run is by commenting out the <code> if ( $capdate < $enddate ) qsub $HOMDIR/gcm_run.j</code> at the end of the script, which will prevent the script from being resubmitted, or rename the script file. You may eventually want to tune parameters in the <code>CAP.rc</code> file 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.

Submit the job with <code>qsub gcm_run.j</code>. You can keep track of it with <code>qstat</code> or <code>qstat | grep ''USERID''</code>, or stdout with <code>tail -f /discover/pbs_spool/''JOBID''.OU</code>, ''JOBID'' being returned by <code>qsub</code> and displayed with <code>qstat</code>. Jobs can be killed with <code>qdel ''JOBID''</code>. The standard out and standard error will be delivered as files to the working directory at the time you submitted the job.

Revision as of 06:32, 3 May 2010 view source Andrew.eichmann (talk \| contribs) 788 edits →Running GEOS-5 ← Older edit		Revision as of 07:46, 3 May 2010 view source Andrew.eichmann (talk \| contribs) 788 edits →Running GEOS-5 Newer edit →
Line 81:		Line 81:


	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~~. ~~Leave END_DATE alone~~ in Fortuna 2.~~0 -- there is a bug that erroneously resubmits~~ the ~~script after this date~~. ~~You can~~ stop the run by commenting out the <code>qsub $HOMDIR/gcm_run.j</code> at the end of the script, which will prevent the script from being resubmitted. ~~Those and~~ the ~~PBS~~ (~~batch system~~) ~~parameters at~~ the ~~beginning are all that you will usually want~~ to ~~change in the script~~.		The script you submit, <code>gcm_run.j</code>, is in ''HOMEDIR''. It should be ready to go as is. The parameter END_DATE in <code>CAP.rc</code> (previously in <code>gcm_run.j</code>) can be set to the date you want the run to stop -- this works in Fortuna 2.1 where it did not in Fortuna 2.0. Also in Fortuna 2.1, you may edit the <code>.rc</code> files directly instead of template (<code>.tmpl</code>). An alternative way to stop the run is by commenting out the <code> if ( $capdate < $enddate ) qsub $HOMDIR/gcm_run.j</code> at the end of the script, which will prevent the script from being resubmitted, or rename the script file. You may eventually want to tune parameters in the <code>CAP.rc</code> file 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.

	Submit the job with <code>qsub gcm_run.j</code>. You can keep track of it with <code>qstat</code> or <code>qstat \| grep ''USERID''</code>, or stdout with <code>tail -f /discover/pbs_spool/''JOBID''.OU</code>, ''JOBID'' being returned by <code>qsub</code> and displayed with <code>qstat</code>. Jobs can be killed with <code>qdel ''JOBID''</code>. The standard out and standard error will be delivered as files to the working directory at the time you submitted the job.		Submit the job with <code>qsub gcm_run.j</code>. You can keep track of it with <code>qstat</code> or <code>qstat \| grep ''USERID''</code>, or stdout with <code>tail -f /discover/pbs_spool/''JOBID''.OU</code>, ''JOBID'' being returned by <code>qsub</code> and displayed with <code>qstat</code>. Jobs can be killed with <code>qdel ''JOBID''</code>. The standard out and standard error will be delivered as files to the working directory at the time you submitted the job.