Running and exploring an existing UKCA Job
Getting hold of an existing UM-UKCA job
Before you can start using UKCA (and the UM generally), you first need to copy a UM or UKCA job from somewhere. You may be given a job from someone for a specific purpose, or you may just copy a standard job. In the UMUI there are two repositories of standard jobs, under the umui and ukca UMUI users. The umui user contains a series of standard jobs provided and maintained by NCAS-CMS. The ukca user contains jobs provided by the UKCA team.
Make a new experiment and take a copy of the UKCA Tutorial Base Job, filter for the ukca user and choose the correct experiment for the machine that you will be running on (HECToR: xxxx, MONSooN: xxxx). Select the a job, labeled Tutorial Base UM-UKCA Job and copy this one to your own experiment.
More detail on how to copy UMUI jobs can be found on the NCAS-CMS Introduction to the UMUI tutorial video.
Running a UMUI job
You will need to change a number of options within the UMUI to allow you to run this job successfully, such as your username, HECToR TIC code (if needed) etc. If you are using the MONSooN job you may also need to change the project group in
Model Selection -> Post Processing -> Main Switch + General Questions
if you want to send output data to the /nerc data disk (this is advisable).
Once you have made these changes you can submit your job. First click Save, then Process, and once this has completed, click Submit. This will then extract the code from the FCM repositories and submit them to the supercomputer. If you are running on MONSooN you will need to enter your passcode at this stage.
Checking the progress of a running job
Log-in to the supercomputer, and check that your job is running. For HECToR do
qstat -u $USER
and for MONSooN do
llq -u $USER
This should give a list of your running jobs. For example, on MONSooN you should get something like
$ llq -u $USER Id Owner Submitted ST PRI Class Running On ------------------------ ---------- ----------- -- --- ------------ ----------- mon001.64641.0 nlabra 6/5 12:36 R 50 parallel c139 1 job step(s) in query, 0 waiting, 0 pending, 1 running, 0 held, 0 preempted
You can also check how far a job has gone while it is running. To do this you will need to cd into the job directory. When you do this, you will see something like this
$ ls baserepos/ pe_output/ umrecon/ xhklg.apstmp1 xhklg.astart xhklg.out xhklg.stash xhklg.xhist xhklga.pc19920901 bin/ umatmos/ umscripts/ xhklg.apsum1 xhklg.list xhklg.requests xhklg.umui.nl xhklga.da19920921_00 xhklga.pe1992sep
Now cd into the pe_output/ directory and do
$ tail -f jobid.fort6.pe0 | grep Atm_Step
Atm_Step: Timestep 1744 Model time: 1992-09-25 05:20:00
Atm_Step: Timestep 1745 Model time: 1992-09-25 05:40:00
Atm_Step: Timestep 1746 Model time: 1992-09-25 06:00:00
Atm_Step: Timestep 1747 Model time: 1992-09-25 06:20:00
Atm_Step: Timestep 1748 Model time: 1992-09-25 06:40:00
Atm_Step: Timestep 1749 Model time: 1992-09-25 07:00:00
(changing jobid as appropriate for your job).
==
