Changes between Version 1 and Version 2 of UM/RunningUMOnArcher


Ignore:
Timestamp:
03/07/15 15:35:39 (4 years ago)
Author:
ros
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • UM/RunningUMOnArcher

    v1 v2  
    11[[PageOutline(1-2)]] 
    22 
    3 = Running the UM on HECToR = 
     3= Running the UM on ARCHER = 
    44 
    5 To run a UM experiment on HECToR you need: 
     5To run a UM experiment on ARCHER you need: 
    66 
    77 1. to have an account on PUMA in order to access the UMUI (UM User Interface) (see [wiki:PumaService PUMA service] to request an account) 
    8  2. to have an account on HECToR (see the FAQ [wiki:FAQ_T3_F6 How do I get a HECToR user account?]) 
    9  3. completed the instructions for [wiki:UM/SettingUpHectorEnv setting up your HECToR environment] 
     8 2. to have an account on ARCHER (see the FAQ [wiki:FAQ_T3_F6 How do I get a ARCHER user account?]) 
     9 3. completed the instructions for [wiki:UM/SettingUpHectorEnv setting up your ARCHER environment] 
    1010 
    1111== Running a Sample UM Job == 
    1212 
    13 There are sample HECToR jobs for all supported versions of the UM on the PUMA UMUI under the userid ''umui''. Use these sample jobs to check that a standard job runs before running your own UM experiments. 
     13There are sample ARCHER jobs for all supported versions of the UM on the PUMA UMUI under the userid ''umui''. Use these sample jobs to check that a standard job runs before running your own UM experiments. 
    1414 
    1515 * Copy a sample job on the PUMA UMUI (The [wiki:UmTraining/IntroToUMUI introduction to the UMUI video tour] shows you how to do this if you are unsure) 
     
    2121     - **Account name/Tic code** 
    2222   - ''Model Selection->FCM Configuration->FCM Extract and Build directories and Output levels'': 
    23      - **Target machine root extract directory**: Set this to location in you home directory on HECToR. E.g. /home/n02/n02/ros/um 
     23     - **Target machine root extract directory**: Set this to location in you home directory on ARCHER. E.g. /home/n02/n02/ros/um 
    2424     - **Local machine root extract directory**: Check that this is set to $HOME/um/um_extracts 
    2525 
    2626 * Click `save` and `process` the job in the UMUI which creates the UM scripts locally. 
    2727 
    28  * Click the `submit` button to submit the job to HECToR. \\ 
    29    A window will pop up detailing progress of the job submission and should always be checked for errors before closing. It also gives details of where your compilation and model output will be sent to on HECToR. 
     28 * Click the `submit` button to submit the job to ARCHER. \\ 
     29   A window will pop up detailing progress of the job submission and should always be checked for errors before closing. It also gives details of where your compilation and model output will be sent to on ARCHER. 
    3030 
    31  * Log onto HECToR and run the command `qstat -u <username>` to follow the job in the queues. 
    32    - the compile stage will run in the HECToR serial queue. 
     31 * Log onto ARCHER and run the command `qstat -u <username>` to follow the job in the queues. 
     32   - the compile stage will run in the ARCHER serial queue. 
    3333   - the reconfiguration (if requested) and the run stage will be automatically submitted after the compilation stage and will run in the parallel queues. 
    3434 
    35  Wait until both your serial job (the compilation and build phase) and your parallel job has finished. If nothing appears when you run `qstat -u <yourusename>`, then HECToR has finished doing what you asked it to do. 
     35 Wait until both your serial job (the compilation and build phase) and your parallel job has finished. If nothing appears when you run `qstat -u <yourusename>`, then ARCHER has finished doing what you asked it to do. 
    3636 
    3737 * Check the output files (details of which were given when you submitted the job) to ensure that the run completed successfully. 
     
    4141 * You have not specified the correct NCAS sub-project allocation in the UMUI as a TIC/Account code. Use the command `groups` on HECToR to see what sub-projects you have access to. 
    4242 
    43  * The job is trying to use some disk space on HECToR where either you do not have any, or sufficient, disk space allocation. Read the information about [wiki:FAQ_T3_F10 NCAS HECToR disk organisation] before contacting g.m.s.lister@reading.ac.uk 
     43 * The job is trying to use some disk space on ARCHER where either you do not have any, or sufficient, disk space allocation. Read the information about [wiki:FAQ_T3_F10 NCAS HECToR disk organisation] before contacting g.m.s.lister@reading.ac.uk 
    4444 
    4545== Running your own Job == 
     
    5050 
    5151 * What disk areas the job uses 
    52  * Do you have permission to access all the files (mods, dumps, ancillary files) on HECToR? 
     52 * Do you have permission to access all the files (mods, dumps, ancillary files) on ARCHER? 
    5353 * Are the resources sufficient, CPU time, number of processors, memory, disk space? 
    5454 * Are the science settings what you need or want? 
    5555 * Are the diagnostics (STASH ) set up as you need them to analyse the experiment results? 
    56  * If you are copying a job that was run on a platform other than HECToR, are all the input files present on HECToR? 
     56 * If you are copying a job that was run on a platform other than ARCHER, are all the input files present on ARCHER? 
    5757 
    5858** What might fail: ** 
    5959 
    60   * You could run out of HECToR resources, insufficient disk space or CPU time. 
     60  * You could run out of ARCHER resources, insufficient disk space or CPU time. 
    6161  * The model may crash in the middle of a run. The reason for this is not always easy to determine. Read the [wiki:Docs/MetOfficeDocs UM User Guide] and look at the [wiki:UmTraining NCAS training material] and explore the `help` buttons in the UMUI to see if there are restrictions or limitations associated with what you are trying to run. 
    6262 
     
    7575  * Do a final `check setup` and correct any reported problems. 
    7676 
    77 === Do NOT use PP Packing on HECToR === 
     77=== Do NOT use PP Packing on ARCHER === 
    7878 
    7979In the UMUI, go to ''Sub Model Independent > Post processing > Initialization and Post Processing of mean and standard PP files''. Ensure that the "Unpacked, profile 0" button is highlighted and that each entry in the table has packing profile zero. Failure to do this will result in illegal numbers ("Not a Number" or Nan) in the diagnostic STASH output.