Release Job RJ4.0

This page documents the vn8.4 GA4.0 release job RJ4.0 (x???? on MONSooN and x???? on ARCHER). This job has been developed by Luke Abraham.

This job is a development of Release Candidate RC6.0 and Release Candidate RC6.2.

Suitability for Release

Tropospheric Chemistry	Users should note the tropospheric OH biases
Stratospheric Chemistry	Users should note the low stratospheric NOy.
Tropospheric Aerosol	Surface properties are green, while column properties are amber
Stratospheric Aerosol

Key

Release candidate still under evaluation

Release candidate not scientifically suitable to be released

Release candidate is suitable for development jobs, and may be scientifically suitable to be released for some applications

Release candidate scientifically suitable to be released

Release candidate does not consider the required chemistry or aerosol processes

Overview

	MONSooN job x????	ARCHER job x????
UKCA branch used	fcm:um_br/pkg/Config/vn8.4_UKCA@16827	fcm:um_br/pkg/Config/vn8.4_UKCA@16827
Decomposition	12EW x 16NS on 6 nodes (see here)	12EW x 12NS on 12 nodes (see here)
Run-time (per model month)	~2 hours (see here)	~2 hours (see here)
Job-step (recommended)	1 model month in 10800 seconds (3 hours)	3 model months in 28800 seconds (8 hours)
Cost (per model year)	150 node-hours (see here)	110 kAU (see here)
Storage Requirements (current STASH settings)	110GB per model year (32-bit pp-files & seasonal 64-bit dumps) MOOSE costs: £12.01 per model year	110GB per model year (32-bit pp-files & seasonal 64-bit dumps) copied to the /nerc disk as the model runs, using the branch fcm:um_br/dev/luke/vn8.4_hector_monsoon_archiving_ff2pp/src as a central script modification.

Results (MONSooN)

MOOSE

Further information on how to use MOOSE can be found on the collaboration twiki.

Note: If you take a copy of this job and run it, you must first manually make the MOOSE set to hold the data in the archive. This is done by

 moo mkset --project-owner=project-YOUR_MONSooN_PROJECT -v moose:/crum/jobid

For instance, if you were in the UKCA project you would have --project-owner=project-ukca. This can be done after the job has started running. The archiving intelligently knows which files need archiving through the use of files named archive_XXXXXX.do. The files also control the deleting of files and dumps once they have been archived or are no longer needed. If, for some reason, the files cannot be archived (e.g. MOOSE is down or the set has not yet been made) then the files will not be deleted. They will continue being generated and existing on the /projects disk until they can be archived.

You should not need to do anything with the fieldsfiles until the whole simulation has been completed (in this case, the whole 15-years). When it does you will find that, while the climate mean files and dumps have been archived, the last files in the e.g. *.pa* or *.pb* streams etc will not have been. You will need to archive these manually by, e.g.

moo put -f -vv -c=umpp jobida.pzYYYYmmm moose:/crum/jobid/apz.pp/jobida.pzYYYYmmm.pp

Where the -c=umpp converts the files from 64-bit fieldsfiles to 32-bit pp-files. Remember to put the .pp at the end of the name of the file in the set on MOOSE.

Evaluation Suite Output (MONSooN)

These were generated from the UKCA Evaluation Suite available on the MONSooN post-processor.

Lightning NOx

The lightning NOx produced in these years was

• ARCHER = 3.98946 Tg(N)/year
• MONSooN = 3.93295 Tg(N)/year