Changes between Version 1 and Version 2 of Docs/AutomaticResubmission


Ignore:
Timestamp:
22/01/13 11:02:46 (8 years ago)
Author:
ros
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Docs/AutomaticResubmission

    v1 v2  
    99Set up your UM job via the UMUI. You will need to specify 
    1010 
    11  a) the run length: **//submodel independent -> start date and run length options//**[[br]] 
    12  Set the run to be the total time of your experiment. 
     11a) the run length: **//submodel independent -> start date and run length options//**[[br]] 
     12 Set the `target run length` to be the total time of your experiment. 
    1313 
    14 b) the job resources for your runs [[br]] 
    15 **//submodel independent -> job resources//** [[br]] 
    16 setting the job time limit to be the length of time needed to run a chunk of your experiment. Then press `NEXT` at the bottom of the window to set up automatic resubmission. Select `automatic resubmission` and specify the target run length and job time limit for the chunks.  
     14b) the job resources for your runs: **//submodel independent -> job resources//** [[br]] 
     15 Set the `job time limit` to be the length of time needed to run a chunk of your experiment. Then press `NEXT` at the bottom of the window to set up automatic resubmission. Select `automatic resubmission` and specify the `target run length` and `job time limit` for the chunks.  
     16 
     17c) the restart dump frequency: **//atmosphere -> control -> post processing dumping and meaning -> dumping and meaning//** [[br]] 
     18 Specify a `restart dump frequency` in days/hours/timesteps. This restart dump frequency must be chosen so that you have a restart dump at the end of each chunk of the run. So for example if you are running a 3 year experiment in 6 month chunks and you are using 360 day years then a suitable restart dump frequency would be 30 days. You may also need to worry about climate meaning which depends on the restart dump frequency (see the UM document about climate meaning). The standard UM scripts are set up so that you can automatically delete superseded restart dumps only when you have archiving switched on via **//submodel independent -> post processing -> main switch and general questions//** (see the document describing automatic archiving for the UM). 
     19 
     20You can now submit this initial run in the normal way and when complete you should find only the first chunk has run, leaving some history files (*.*hist) and either all the restart dumps and the post processing files specified via STASH if automatic archiving has not been used or the last restart dump only if archiving is switched on and deletion of superseded dump files selected. 
     21 
     22== Continuation Run 
     23 
     24When you process jobs using the UMUI it produces a set of UNIX scripts on the local computer where you run the UMUI. These scripts should be in the directory 
     25`$HOME/umui_jobs/<jobid>`. To create a continuation run: 
     26 * edit the UM script called `SUBMIT` in this directory 
     27 * change the line `TYPE=NRUN` to `TYPE=CRUN` 
     28 * if your initial run was a compile and run job in one job then you need also to change to `STEP=4` in the `SUBMIT` script as well. 
     29 * save and exit 
     30 * resubmit the UM run as you did for the initial run. 
     31 
     32The run should continue from where the initial run finished and then each of the chunks should submit themselves automatically without further intervention. 
     33 
     34**NB 
     35 
     36 * The maximum time limits for the standard queues on HECToR are 1,  3, 6 and 12 hours 
     37 * Without automatic archiving disk space can fill up and cause the job to crash.