Changes between Version 6 and Version 7 of Docs/AutomaticResubmission


Ignore:
Timestamp:
16/04/15 17:53:54 (4 years ago)
Author:
annette
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Docs/AutomaticResubmission

    v6 v7  
    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 `target run length` to be the total time of your experiment. 
     11a) The run length: //Input output control and resources -> 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: **//submodel independent -> job submission, resources etc//** [[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.  
     14b) The job resources for your runs:  
     15 * **Pre UM vn8.2**: //Input output control and resources -> Job submission, resources etc// [[br]] 
     16    Set the `job time limit` to be the length of time needed to run a chunk of your experiment.[[br]] 
     17    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.  
    1618 
    17 c) 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 [wiki:Docs/ClimateMeaning 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 * **UM vn8.x**: //User information and submit method -> Job submission method//[[br]] 
     20    Press `Qsub` at the bottom of the window then set `job time limit` to be the length of time needed to run the initial chunk of the experiment.[[br]] 
     21    Then press `Back` and `Resubmit` and specify the `target run length` and `job time limit` for the continuation chunks.  
    1922 
    20 You 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. 
     23c) The restart dump frequency: //Atmosphere -> control -> post processing dumping and meaning -> dumping and meaning// [[br]] 
     24 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.  
     25 You may also need to worry about climate meaning which depends on the restart dump frequency (se the document about [wiki:Docs/ClimateMeaning Climate Meaning]).  
     26 
     27d) Archiving settings: //Post processing -> main switch and general questions// [[br]] 
     28 The standard UM scripts are set up so that you can automatically delete superseded restart dumps only when you have archiving switched on (see the document about [wiki:Archer/NercArchiving Archiving]). 
     29 
     30**Note:** At UM vn 6.6.3 the ''Start date and run length options'', ''Job submission and resources'', and ''Post processing'' windows can be found under ''Submodel Independent'' 
     31 
     32You can now submit this initial run in the normal way. When complete you should find only the first chunk has run, leaving some history files (*.*hist) and either i) all the restart dumps and the post processing files specified via STASH if automatic archiving has not been used, or ii) the last restart dump only if archiving is switched on and deletion of superseded dump files selected. 
    2133 
    2234== Continuation Run == 
     
    4759 * Then SAVE, PROCESS and SUBMIT 
    4860 
    49 **UM vn8.2 onwards** 
     61**UM vn8.x** 
    5062 
    5163 * In the UMUI navigate to ''Compilation & run options → compile & run options for atmos & recon''