This is a very basic guide to getting a UM 8.6 SCM model to run on the ARCHER post processing machine. At this stage it's an aide memoire for me as much as anything. This requires a low degree of hacking - this could be removed by creating some hand edits in the future.

The UMIU job is xlmjb. The SCM specific settings are in Model Selection → Atmosphere → Model Resolution and Domain → Horizontal, and Single Column Settings (for the SCM namelist and output file)

Set it up to extract and build the model and submit it to ARCHER. qdel the job before it starts to build - we need to build the model to run serially on the post processor machine.

ssh to the post processor machine —

ssh espp1

Go to the target machine route directory and then find the cfg subdirectory (/home/n02/n02/grenvill/um/xlmjb/umatmos/cfg in my case)

Make sure you have the intel programming environment loaded and that you swap to intel/ before using.

module swap PrgEnv-cray PrgEnv-intel
module swap intel/ intel/

You will need to change bld.cfg so that it builds a model linked to the serial communications library (/work/n02/n02/hum/gcom/intel/gcom4.5/archer_intel_serial) and, since some module information doesn't work on the post-processor (see, you need to specify netcdf library paths explicitly. Use /home/n02/n02/grenvill/um/xlmjb/umatmos/cfg/bld.cfg as an example config file.

Then build the model

fcm build 

My executable was created in /home/n02/n02/grenvill/um/xlmjb/umatmos/bin - yours will be similarly.

The path to and name of the executable should be typed in the UMUI window in the model compile and run options (Model Selection → Compilation and Run Options → Compile and Run options for Atmosphere…) , and the UMUI now set to run the model ie switch off extraction and compilation.

Submit the job to ARCHER and again qdel the job to prevent it from trying to run.

Go to the umui_runs directory just created, add to CNTLATM the namelist


just before


I don't know why the SCM needs the RUN_Eng_Corr namelist because it's not used - this may be just an issue for this particular job (I don't know its provenance)

To run the model type

./umuisubmit_run 2>&1 | tee your-trace-file

where your-trace-file is a file of your choice which will hold stderr and stdout outut.

The contents of the umui_runs directory get deleted after the model completes - this behaviour can be changed.

Last modified 2 years ago Last modified on 10/06/15 16:34:15