Difference between revisions of "UKCA & UMUI Tutorial 3"
Line 24: | Line 24: | ||
on HECToR. This is also a handy list of all the fields that can be outputted from the model, which is easier to search than by going through the UMUI panels. |
on HECToR. This is also a handy list of all the fields that can be outputted from the model, which is easier to search than by going through the UMUI panels. |
||
+ | |||
+ | ==Output Files== |
||
+ | |||
+ | Before we cover outputting diagnostics from the UMUI STASH panel, we will first cover the different output fields files that are produced by the UM. Output from STASH is sent to different output streams, and there are two types of files used by these streams: '''standard PP files''' and '''climate mean files'''. |
||
+ | |||
+ | ===Standard PP files=== |
||
+ | |||
+ | [[Image:UMUI_PostProc_PPfiles.png|thumb|300px|right|Figure 1: The initialization and processing of PP files UMUI panel.]] |
||
+ | In your UMUI job, go to ''Model Selection → Post Processing → Initialization and processing of mean and standard PP files''. As well as choosing the packing profile (see the '''Help''' button for more information) this panel also describes how these different files are treated. As can be seen in Figure 1, there are 11 PP files defined, '''PP0''' to '''PP10''', which correspond to designators '''pa''' to '''pk''' (with units 60-69, and 151 - these unit numbers may be important in warning and error messages). |
||
+ | |||
+ | The table in this panel can be used to set various properties of these files, such as the time period the file covers, and whether or not the file is archived (i.e. either to the <tt>archive/</tt> sub-directory or RDF facility on HECToR, or two the <tt>/nerc</tt> disk or MOOSE on MONSooN). Being able to change the time period is very useful - while for many simulations monthly mean files are preferred (see the discussion about ''climate meaning'' below), often you may wish to output higher frequency data, e.g. 6-hourly. These PP files are limited to a finite size and so outputting a month of 6-hourly data may cause the model to crash at run-time. The solution to this is to change how frequently the files are generated, e.g. you could output daily files instead of monthly ones. |
||
+ | |||
+ | ===Climate Mean files=== |
||
+ | |||
+ | [[Image:UMUI_DumpMean_Main.png|thumb|300px|right|Figure 2: The dumping and meaning main UMUI panel.]] |
||
+ | [[Image:UMUI_DumpMean_NEXT.png|thumb|300px|right|Figure 2: The dumping and meaning follow-on UMUI panel.]] |
Revision as of 13:34, 11 June 2013
What is STASH?
STASH is the Unified Model's storage handling and diagnostic system. It is designed to cope with the many different configurations that the UM can be used in, but still provide output in a consistent and standard way.
Prognostic and Diagnostic Fields
The UM considers variables (or fields) to be of two different types, prognostic or diagnostic. Prognostic fields are ones which the model must have values for, prior to each timestep, as the equations of motion the model solves require these fields (these are fields such as specific humidity or potential temperature) so they must exist in the model start dump. Diagnostic fields are all other fields that are derrived from prognostic ones, and as such the model does not need to have prior values for these. Ancillary files (such as emissions, SSTs etc) contain prognostic fields.
From a user's perspective, STASH is used to output fields during the run, and from this point of view it does not matter if these are prognostic or diagnostic fields. However, you will need to consider these differences when you add new chemical tracers.
STASH Sections and Items
Each field that is considered by STASH has a unique address which is given by a section and an item number. Prognostic fields are mostly held in section 0 (with the exception of tracers) and diagnostics are organised by areas of the code, e.g. short-wave radiation diagnostics are held in section 1, long-wave radiation diagnostics are held in section 2 etc. Some sections will always be on, and some sections will only be on if a certain process is selected, e.g. the interactive land-surface scheme. Each section can hold up to 512 items, where each item is a separate prognostic or diagnostic field, and can be either 2D or 3D.
Each field has its own entry in a STASHmaster file. There is a master list of fields which is held in the STASHmaster_A file, which is located at
/projects/um1/vn8.2/ctldata/STASHmaster/STASHmaster_A
on MONSooN, and at
/work/n02/n02/hum/vn8.2/ctldata/STASHmaster/STASHmaster_A
on HECToR. This is also a handy list of all the fields that can be outputted from the model, which is easier to search than by going through the UMUI panels.
Output Files
Before we cover outputting diagnostics from the UMUI STASH panel, we will first cover the different output fields files that are produced by the UM. Output from STASH is sent to different output streams, and there are two types of files used by these streams: standard PP files and climate mean files.
Standard PP files
In your UMUI job, go to Model Selection → Post Processing → Initialization and processing of mean and standard PP files. As well as choosing the packing profile (see the Help button for more information) this panel also describes how these different files are treated. As can be seen in Figure 1, there are 11 PP files defined, PP0 to PP10, which correspond to designators pa to pk (with units 60-69, and 151 - these unit numbers may be important in warning and error messages).
The table in this panel can be used to set various properties of these files, such as the time period the file covers, and whether or not the file is archived (i.e. either to the archive/ sub-directory or RDF facility on HECToR, or two the /nerc disk or MOOSE on MONSooN). Being able to change the time period is very useful - while for many simulations monthly mean files are preferred (see the discussion about climate meaning below), often you may wish to output higher frequency data, e.g. 6-hourly. These PP files are limited to a finite size and so outputting a month of 6-hourly data may cause the model to crash at run-time. The solution to this is to change how frequently the files are generated, e.g. you could output daily files instead of monthly ones.