Introduction to the UNICOS CCM processor.

NCAR/TN-383+IANCAR TECHNICAL NOTE

December 1992

Introduction to the UNICOSCCM Processor

LAWRENCE E. BUJA

CLIMATE AND GLOBAL DYNAMICS DIVISION

NATIONAL CENTER FOR ATMOSPHERIC RESEARCHBOULDER, COLORADO

III

I

CONTENTS

List of Figures . . . . . . . . . . . . . . . . . . . . .

Preface . .. . . .. .

1.0 Introduction .........

2.0 Processor Job Scripts .......

2.1 A Sample Processor Job Script ....2.2 General Notes on ICP Usage ....2.3 Jobstepping ........2.4 Running the Processor on the Cray ..2.5 Accessing the Sample Processor Job Scripts2.6 Online Documentation .....2.7 Getting Help .......

3.0 Use of Input Control Parameters ....3.1 Eleven More Examples of Common Combinations3.2 A Brief List of Processor Options ......3.3 List of Fields Available for Processing ..3.4 User-Defined Derived Fields . ...

4.0 Processor Usage .......4.1 CCM2 Considerations ......

4.2 Processor file management4.3 Error Handling4.4 Processor Output ..... .4.5 Graphical Output ......4.6 Printed Output ... ...

of ICPs· · ,

· · ,

· · ·

v

... . . . vii

1

. 3·..... · 4

678

9... . .10... . . . 10

... . . . 11

... . . .11

..... . 28

..... . 43

..... . 49

. . . . . . 51·.· · ·. ·. 51

... . . 51...... 52

· . . . . 53...... 53...... 53

5.0 Summary ............. . 58

References ... . . . . ...

Glossary . . . . . . . . . . . .. . .. . . 59. . . . . .60

111

· · · · · · · · · · · ·

· · · · · · · · · · · ·

List of Figures

Data flow through the Processor.

Time Average of T at 1000 mb from 30-day-ave. sh.

Index of plots from compare-aves. sh.

Index of plots from rd-savetape. sh.

Graphical output from plt-diffs.sh.

Printout from the generic job script.

Index of plots from the first example script, plot. sh.

Horizontal plot of temperature at 850 mb on day 11.0.

.· · · · · · · · 2

... . . . . . . 15

... . . . . .. 17

... . . . . . . 19

... . . . . . . 21

... . . . . 54-56

. . . . . . . . .57

......... 57

v

Fig. 1.

Fig. 2.

Fig. 3.

Fig. 4.

Fig. 5.

Fig. 6a-c.

Fig. 7.

Fig. 8.

Preface

This technical note provides an introduction to the CCM Modular Processor, a post-processing software package. The Processor analyzes datasets such as the history tapes(Mass Storage volumes) output by the NCAR Community Climate Model (CCM), theinput and boundary datasets used to initialize CCM2 and observational datasets whichare written in CCM history tape format. This document is designed as a tutorial to teachnew users how to access the Processor and complete simple tasks, and as a quick referenceguide for more experienced users. The user is assumed to have at least a brief knowledgeof the UNIX computing environment.

This introductory document is not a comprehensive description of the Modular Pro-cessor, but an introduction to assist users in the practical aspects of accessing and usingthe Processor. This will enable the new user to begin using the Processor and completesimple tasks. Detailed documentation about the more advanced capabilities of the Pro-cessor is givenin "CCM Modular Processor User's Guide", NCAR/TN-290+IA.

This note makes the earlier document "Introduction to the CCM Modular Processor(Version PROC02)" NCAR/TN-289+IA, obsolete.

vii

INTRODUCTION TO THE CCM MODULAR PROCESSOR

1.0 Introduction

The CCM Modular Processor is a batch tool for the analysis of model or observationaldata. Most frequently the data is in one of 4 history tape formats output by a version ofthe NCAR Community Climate Model (CCM). The data on these files are input to theProcessor, manipulated, and output in various forms, according to a series of user-specifiedrequests. The Processor is capable of performing the following functions:

1) Analysis of Individual Time Samples (including time series)2) Time Averaging3) Ensemble Averaging4) Time Filtering5) Case Comparison

6) Zonal Averaging7) Meridional Averaging8) Vertical Averaging9) Horizontal Area Averaging

10) Land/Ocean/Sea-ice Masking11) Horizontal Plotting12) Meridional Cross-Section Plotting

13) Latitudinal Cross-Section Plotting

14) Time Series Plotting

15) Computing New Fields

16) Spectral Operations

a. Bandpass Filtering

b. Horizontal Transformation and Truncation

c. Spectral Diagnostics and Graphics

Many types of data input to the Processor are allowed. These include:

* pressure history save tapes,* time average history save tapes,* time series history save tapes,* time average save tapes,* time series save tapes,* time series plot save tapes,* List Sorted Data (LSD) save tapes.

1

The history tapes (produced by the model or processor) and the save tapes (produced

by the processor) each have a unique format. Descriptions for the history tapes formats

are published in the appropriate users guides for the corresponding versions of the CCM

(see References on page 59). The formats for pressure history tapes and the various types

of save tapes are given in the CCM Processor Users Guide.

The Processor is also capable of producing all of the above tape types, with the ex-

ception of obsolete CCMOA history tapes. Additionally, the Processor outputs another

type of save tape, one which contains only horizontal slices, and is referred to as a hor-

izontal slice save tape. The format of this tape is the easiest for the user to read with

a FORTRAN program for the users own external processing or for transmittal to other

institutions. Figure 1 summarizes the data flow through the Processor.

Fig. 1. Data Flow through the Processor. Output from the CCM, in the form of history tapes,

is input to the Processor. Depending on user requests, the output data may take on any

of the forms shown. History tapes, time average save tapes, time series save tapes, and

time series plot save tapes can be input back into the Processor for further processing.

Horizontal slice save tapes are in a convenient form to input to other user codes.

2

2.0 Processor Job Scripts

This section introduces the Processor with a sample Processor job script. This codewill familiarize users with the format of a Processor run script and can be used as a

template to build more complicated job scripts. Instructions for accessing copies of thissample Processor script, as well as a number of other samples, are given in section 2.5.

To use the Processor, you will run the UNICOS script, /ccm/proc/Processor, on

the NCAR Cray. This script first copies your Processor Input Control Parameter (ICP)

instructions into a file called parms, then calls the executable version of the Processor.

Once running, the Processor will look for the file parms, check the contents for correct

syntax, then carry out the instructions given in the file.

The basic structure of any Processor script will be of the form:

1 #!/bin/csh2 #QSUB -q econ -eo3 cd $TMPDIR45 cat >! parms << 'END'6 PROCESSOR INPUT CONTROL PARAMETERS7 'END'89 /ccm/proc/Processor

10 exit

where:

Lines 1-2 are Cray UNICOS shell commands controlling job execution in the batch queues

(See the SCD document NCAR UNICOS Primer for more details).

Line 3 ensures that the Processor is run in an empty, temporary directory.

Line 5 copies the Processor's ICPs into the file parms in the $TMPDIR directory.

Line 6 represents a group of Processor ICP keywords that determine which processing

tasks are carried out. The ICPs are all the instructions following the cat >! parms <<

'END' and preceding the next 'END' in the run script. ICPs are the means by which you

specify what you want the Processor to do. See the listing of the file plot. sh in Section

2.1 for an example of ICP usage.

Line 7 is the target for the cat command in line 5. When the cat command encounters

the string 'END', it stops putting text into the file parms.

Line 9 runs the Processor. The Processor will first check the ICPs for correct syntax, then

carry out the instructions defined by the ICPs

Line 10 exits the script.

3

2.1 A Sample Processor Job Script

The following sample Processor script, plot. sh, provides an example and line-by-line

description of how ICPs can be combined together to do the following:

* input days 11.0 through 15.0 from CCM2 history tape /CSM/ccm2/414/hist/h0002,

* for these days, read the temperature (T) field which is on model levels,

* interpolate T from the model levels to the specified pressure levels,

* produce horizontal plots of T on the specified pressure levels,

* dispose the plot file to MP, the Scientific Computing Division (SCD) laser printer.

The output job log and a sample plot for plot. sh are shown in Figs. 6-7 on pages 54-57.

1 #!/bin/csh instructs the Cray UNICOS shell to run under the C-shell.

2 The #QSUB command supplies instructions to the batch queue controller. Here, the

-q econ runs this job in the economy queue. Time limits are 30 seconds for each

process (-it 30) and 33 seconds for the entire job (-IT 33). Memory limits are 2

Megawords for each process (-lm 2mv), as well as for the entire job (-IM. 2Mw). The

-eo combines both the diagnostic and the printed output into a single output file.

3 cd $TMPDIR makes $TMPDIR the current directory that the job will be run from. It is

important that the Processor is run from an empty directory such as $TMPDIR, since

extra files left in the working directory from previous runs can cause conflicts.

4

plot.sh

1 #!/bin/csh2 #QSUB -q econ -It 30 -IT 33 -lm 2Mw -lM 2Mw -eo3 cd $TMPDIR45 cat >.! parms << 'END'6 C7 C plot.sh read temperature from a history tape and plot8 C9 TITLEA = 'Plot.sh: 850,500,200mb T from the CCM2 Control Run'

10 TAPESA = '/CSM/ccm2/414/hist/h0002'11 DAYSA = 11.,12.,13.,14.,15.12 FIELDA1 = 'T'13 PRESSLE = 850.,500.,200.14 HPROJ = 'RECT'15 HPCINT = 'T',850 ,5., 'T',500.,10., 'T',200.,0.16 DPLTMF = 'MP'17 ENDOFDATA ---------- ---------------------------18 'END'1920 /ccm/proc/Processor21 exit

-- I~~~~-

4 Blank lines are allowed in the UNICOS portion of the script.

5 cat >! parms << 'END' places all the text following line 5 until the line 'END' isencountered (on line 18), into the file parms. The Processor will then read the ICPsfrom parms.

7 Comment lines may be used and are encouraged. Comment lines may be upper orlower case and must start in column one.

9 TITLEA = 'Plot.sh: 850,500,200mb T from the CCM2 Control Run' is a usersupplied title which will appear on all plots and printout.

10 TAPESA = '/CSM/ccm2/414/hist/h0002' is the full Mass Store filename for the in-

put CCM2 history tape which contains the temperature data.

11 DAYSA = 11. ,12.,13., 14. ,15. specifies that these model time samples on the his-

tory tape /CSM/ccm2/414/hist/h0002 will be processed.

12 FIELDA1 = 'T' is the list of names of fields to be processed. In this case it is tem-perature. For a list of available fields for CCM1 and CCM2, see section 3.

13 PRESSLE = 850. ,500. ,200. is the list of pressure levels, in millibars, for vertical

interpolation. If this ICP is not present, the default is no interpolation from theinput model levels.

14 HPROJ = 'RECT' specifies that all requested fields are to be plotted and that an equa-torial cylindrical equidistant projection will be used for all horizontal plots.

15 HPCINT = 'T',850.,5.,'T',500.,10., T',200.,0. is an array of triplets used to

specify the contour intervals on horizontal projection plots. In this case, T at the

850 mb level will be plotted with a contour interval of 5.0K, T at the 500 mb levelwith a contour interval of 10.OK, and at the 200 mb level, an appropriate value willbe chosen automatically. There will be a total of 15 plots produced; 3 plots per timeperiod (one for each level) for each of five time periods (days 11.,12.,13.,14.,15.).

16 DPLTMF = 'MP' specifies that the plot file is to be disposed to the SCD high speedlaser printer. The plots may be picked up in room 9A if you are an on-site user.Otherwise it will be mailed back to your remote site within 3-6 days.

17 ENDOFDATA indicates the end of this Processor jobstep.

18 'END' is the target for the cat >! parms << 'END' command.

20 /ccm/proc/Processor runs the Processor. Job accounting is automatically run atthe end of the last jobstep.

21 exit ends the script. You can "store" unused ICP's anywhere after this line.

5

2.2 General Notes on ICP Usage

From the above example, it is clear that there are specific syntax rules for the use of ICPs.

Some of the most important are:

1. The general format is: ICP = VALUE(S).

2. The ICPs TAPESA, DAYSA, and FIELDA1 are all required for ANY processing to be

done.

3. The first ICP line after the cat command must not be blank.

4. Start all new keywords in column 2 or farther right. ICPs may not extend beyond

column 72. Field names must be 8 characters or less.

5. ICPs may be continued to subsequent lines by a trailing comma on the preceding line

or a leading comma on the continuation line.

6. The letter C in column one indicates a comment line.

7. The TYPE of each value (i.e., INTEGER, REAL, or CHARACTER) is important-

follow FORTRAN syntax conventions for the value specifications.

8. Do not use tabs or trailing blanks.

9. All ICPs must be capitalized and all arguments are case sensitive.

10. ICP definitions may span multiple lines.

11. ICPs are order-independent, and each keyword can only be used once in each

jobstep.

12. Each group of ICPs ends with an ENDOFDATA ICP.

The first item to mention is that some ICPs are required input in the script, while

others can be left unspecified, in which case they are automatically set to a default value.

Those keywords which are required have no default value, while all other keywords have

default values assigned to them within the Processor code. A complete description of

all keywords and their defaults is given in the "CCM Modular Processor Users' Guide"

(Wolski, 1987) and its supplement "'PROC02A: Enhancements to the PROC02 Version of

the CCM Modular Processor" (Wolski, 1989)

The Processor automatically transfers data files from the Mass Store to the Cray

disks using the filename specification from the TAPESA ICP. In this example, the file

/CSM/ccm2/414/hist/h0002 is read from the Mass Store System. The DAYSA ICP (re-

quired for history tapes) specifies which model times are to be processed and can either

6

be requested explicitly (e.g., 11.0, 12.0, 13.0, 14.0, 15.0), or in shorter, do-loop nota-

tion (11.0, 15.0, 1.0). The FIELDA1 ICP (required) specifies the fields to process for this

dataset; in this case it is temperature T.

Other ICPs specify how the data will be processed. In this example, HPROJ='RECT'

(default is 'NO') specifies that horizontal projection plots for all levels are plotted on a

rectangular cylindrical equidistant projection. The TITLEA ICP contains the user defined

title for plots and printout of Case A processing. The default is to produce no title.

Some ICPs end in an A, B, or C. Any ICP with such an ending is a case dependentICP. For comparison of two cases (or tapes), Case A and B suffixes are used for ICPs

pertaining to these two tapes, and the Case C suffix applies to the keywords pertaining

either to the comparison of Cases A and B or to the merging of Cases A and B. In the

no comparison case, Case A is used for all case-dependent keywords. The DAYSA ICP

indicates the days for Case A that should be processed.

Those ICPs not ending in a capital A, B, or C are case independent ICPs and

their instructions apply to all cases which are being computed. An example of a case

independent ICP is PRESSLE.

Other ICPs, such as FIELDA1, also have a numeric suffix. The numeric ending indi-

cates a field pass dependent ICP. Field passes allow the user to process input data

over several field 'passes' of the input data, so that enough memory is available for each

pass of the data. The FIELDA1 ICP is also an example of a field and case dependentICP. Memory restrictions limit the number of fields that can be processed in a single

pass. ICPs with no such suffix control processing for all field passes and cases.

2.3 Jobstepping

In cases where the Processor cannot perform the task you wish to complete in one

run, capabilities exist for running multiple Processor runs (or steps) within a singlejob

submission. This is done simply by concatenating the different ICP scripts together, sepa-

rated by ENDOFDATA ICPs. The Processor is executed repeatedly, once for each ENDOFDATA

in the processor script (in the plot. sh example, only one jobstep is run). This capability,

called jobstepping, often saves time submitting jobs that must be processed consecutively.

For example, suppose the job to be performed is a composite of January averages.

Without jobstepping, the composite averaging job would have to be submitted after all

the single jobs were completed. But b jobsteppingre, each step could compute one January

average, while the last step could compute the composite average. This technique can also

be used to avert unnecessary interaction with the Mass Store (by saving the results from

7

one run on the CRAY disk and immediately reaccessing them, rather than disposing tothe Mass Store). Note the provision in the ICP jobstream for jobstepping, by separatingthese two groups of control parameters into two separate processor 'jobs' within the samejob script (each execution of the processor then uses the next script of ICPs). See example10 on page 26 for an example of a multi-step Processor job.

2.4 Running the Processor on the Cray

Remote users will submit jobs via Internet Remote Job Entry (IRJE). The outputwill be returned as per the IRJE protocols. To return plot files to your local computervia IRJE, use the ICPs DPLTMF='UG' and DPLTFN='myplot.plt'. IRJE is recommendedbecause it is designed to keep retrying to return the output when the connections fromNCAR to the users local computer are not functioning. See the SCD document "IRJE:Using the NCAR Internet Remote Job Entry System" for more information.

Interactive users (i.e. users logged onto the Cray interactively) can either run theprocessor interactively or submit jobs to the batch queue with the qsub command. Whenrunning interactively, it should be ensured that the current directory is clean of outputfrom previous Processor runs. Batch job execution process may be traced with the qstat-a command. The batch output will be returned to the directory on the Cray from whichit was submitted.

NCAR users can submit jobs to the Cray via MASNET from their local computerwith the shjob -p plot.sh command. The job's execution may be traced with the rshshavano qstat -a command. The output will be returned according to the file transferprotocols established by you or your system manager. To return your Processor plot filesto your local computer via MIGS, use the following ICPs

DPLTMF = 'IS'

DPLTRCPP = 'my. computer. ucar.edu:/mydisk/myplot.plt'

Local users must have a copy of the file .rhosts in their home directories on both shavanoand their local computer. Issue a cat /ccm/proc/samples/rhosts on shavano.ucar.edu

to see an example .rhosts files.

Users who encounter problems or are unfamiliar with the NCAR job submissionprocedure should contact either their system manager or the NCAR SCD consultants

(303-497-1278) for details about the best methods for job submission and retrieval.

8

2.5 Accessing the Sample Processor Job Scripts

The easiest way to get started is to copy one of the sample Processor scripts, run itto make sure your job submission and retrieval method works, then modify the samplescript for your particular application. Section 3 will examine the twelve sample script filesmaintained on the NCAR's mainframe in the directory /ccm/proc/samples:

plot.sh

initial. sh

one-day.sh

30-day-ave.sh

compare-aves.sh

rd-savetape.sh

pit-diffs.sh

hsl.sh

std-dev.sh

ave-ave.sh

derfld.sh

spectral.sh

read temperature (T) from a CCM2 history tape and plot it.make a CCM2 initial dataset,

process one day for one case,produce a thirty day time average,produce two ten-day time averages and compare them,recompute differences and plots from two save tapes,replot only differences from a save tape.read a history tape, output T to a Horizontal Slice Save (HSL)tape, then read the HSL tape with FORTRAN program.compute standard deviations from four Processor save tapes,produce two five-day time averages and average the resultsMake a simple derived field and plot it.Spectrally truncate a T42 dataset.

There are a number of ways to get copies of these sample codes:

1. If you are a remote user, you can issue the following command from your local UNIXcomputer to print out the the sample codes:

rsh shavano.ucar.edu /ccm/proc/samples/list

To copy individual sample files, such as plot.sh to your local directory, use the UNIX

command:

rcp shavano.ucar.edu:/ccm/proc/samples/plot.sh plot.sh

(Note: An error message of permission denied probably means that you do nothave your .rhosts files configured correctly)

2. If you are logged onto shavano directly, you can copy these sample codes to your own

shavano directory by typing:

cp /ccm/proc/samples/. sh

A number of additional sample ICPs for plotting your data, complete with the re-sulting graphics, can be found in Appendix A of 'CCM Modular Processor User's Guide

(Version PROC02)', NCAR/TN-290+IA. Other sample ICP's are given in section E of

9

1.

2.

3.

4.

5.

6.

7.

8.

9.

10.

11.

12.

Circulation Statistics from Seasonal and Perpetual January and July Simulations with

the NCAR Community Climate Model (CCM1):R15, NCAR/TN-302+STR.

2.6 Online Documentation

Detailed documentation for the Modular Processor is available online to remote UNIX

platforms via the icp command. icp provides summaries and documentation of Proces-

sor ICPs. The command icp target displays the Processor documentation on the ICP

target (i.e. icp daysa will display the explanation of the ICP DAYSA). Numeric sub-

stitution for the field pass number "n" is limited to the number "1". If an ICP matching

target is not found, an icp -k target is automatically attempted. An icp -k target

looks up information on the general category of the word(s) target in a summary of the

ICP definitions. Finally, an icp -s target greps through the entire online Processor

documentation for target.

Remote users can access icp online from their own UNIX platform via the remote

shell command rsh to the SCD front end machine meeker.ucar.edu. The command

would be of the form:

rsh meeker.ucar.edu /crestone/uO/ccmproc2/doc/icp target

where target is the input to the icp command. To run rsh on meeker, the re-

mote user needs an account on meeker.ucar.edu and a valid .rhost file on the user's

meeker. ucar. edu account. Local CGD users can issue the command simple by entering

icp target.

An icp interface to the emacs editor can be obtained via the command

rsh meeker.ucar.edu cat /crestone/uO/ccmproc2/doc/icp.el.

2.7 Getting Help

The NCAR Climate and Global Dynamics Division has historically invested in com-

plete documentation of its community tools, among which include the CCM Modular

Processor, obviating the need for consulting assistance. This documentation has proven

to provide sufficient guidance to those users who invest some time in reading the material.

The CCM Core Group staff can only respond to queries involving documentable errors

(bugs) in the software. If a user should encounter bugs in the code (i.e., it doesn't behave

in a way in which the documentation says it should), the problem should be reported elec-

tronically to [email protected]. Otherwise, the user should rely upon the available

documentation.

10

3.0 Use of Input Control Parameters

Section 3.1 will introduce and briefly explain eleven more sample Processor scriptswhich perform specific functions. The following sections present a brief list of availablekeywords (3.2), a list of all fields available for processing (3.3), and an introduction intothe use of user-defined derived fields (3.4).

3.1 Eleven More Examples of Common Combinations of ICPs

Many common processing jobs result from similar combinations of ICPs. These com-mon tasks can be copied, modified if necessary, and used for your own processing tasks(however, it is advised that you read the full description of each keyword in the Users'Guide before using it). In addition to the first example given in section 2, eleven moreexamples of common processing tasks are:

2. initial.sh make a CCM2 initial dataset.3. one-day. sh process one day for one case.4. 30-day-ave.sh produce a thirty day time average.5. compare-aves. sh produce two ten-day time averages and compare them.6. rd-savetape. sh recompute differences and plots from two History Save Tapes.7. plt-diffs.sh replot only differences from a save tape.8. hsl. sh read a history tape, output T to a Horizontal Slice Save (HSL)

tape, read the HSL tape with FORTRAN and plot the data.9. std-dev.sh compute standard deviations from four Processor save tapes,

10. ave-ave. sh produce two five-day time averages and average the results11. derfld. sh Make a simple derived field and plot it.12. spectral.sh Spectrally truncate a dataset.

The Processor scripts for these examples are discussed in this section. Preceding eachis a brief description of what each script will produce. Following each is a descriptionof the pertinent new options introduced in the example. If these examples are run insequence, they provide examples which can be run as shown. All these examples are avail-able from the /ccm/proc/samples directory on shavano. (see section 2.5 for instructionson accessing this directory).

The complete CCM Modular Processor Users' Guide (Wolski 1987) contains addi-tional samples of plots (Appendix A) and a listing of the ICPs necessary to generate thepictures. Addition examples of ICP decks may be found in "Circulation Statistics fromSeasonal and Perpetual January and July Simulations with the NCAR Community Cli-mate Model (CCM1):R15" (NCAR/TN-302+STR).

11

Example 2. - initial.sh - Make a CCM2 initial dataset.

This job reads the requested fields for model day 15.0 and writes them onto a new history

tape. This is the set of diagnostic fields needed as initial data to start CCM2. One History

Save Tape is made and written to the MSS. No plots are produced.

Example 2 reads in the fields PHIS, PS, ORO, TS1, TS2, TS3, TS4, T, U, V and Q for day

15.0 from the CCM2 control run on tape /CSM/ccm2/414/hist/h0002. SAVHSTA requests

that these eleven variables are then written out in CCM2 time series history tape format

to /USERNAME/ccm2/414/initial/example2. The ICPs PWDHSTA and MSRTO control the

MSS password and retention period of the time series history save tape. This small tape

can then be either used as initial data for a CCM2 model run or read and reprocessed in

subsequent Processor runs.

Some additional keywords associated with reading and writing history tapes are:

TYPEA = 'CCMl' Format of input history tapes.NDYHSTA = 30 Maximum number of days to place on a single tape.PKHSTA = 2 Packing density for output History Save Tapes.BPHSTA = 'NO' Enables history tapes to be written with blocked points.SAVMHST = 'TSR' Output time-average or time-series History Save Tapes.OFTHSTA = 'CCM1' Format for output history tapes.

See the CCM Modular Processor Users' Guide (Wolski 1987) for more details about these

ICPS.

This sample cost 1/200th of a GAU to run as a batch job in the regular queue.

12

CC Example 2. - initial.sh - Make a CCM2 initial dataset. (.00483 GAUS)CC Request the data as in Example 1.C

TITLEA = 'Example 2. - initial.sh - DAY 15'TAPESA = '/CSM/ccm2/414/hist/hO002DAYSA = 15.FIELDA1 = 'PHIS', PS', 'ORO', 'TS','TS2','TS3','TS4', 'T, 'U','V' 'Q'

CC SAVHSTA writes the data out to a Save History Tape.C PWDHSTA is the write password for the History Tape.C MSTRO is the MSS retention period (days) for the History Tape.C

SAVHSTA = '/USERNAME/ccm2/414/initial/example2'PWDHSTA = 'PASSWD'MSRTO = '365'

CENDOFDATA ---------------------------------------

--~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Example 3. - oneday.sh - Process one day.

This job processes one model day for Case A, interpolates the data to seven pressuresurfaces, produces horizontal plots at each pressure level of each field, zonally averagesthe data, then plots and prints the zonal averages (a total of 16 plots are produced).

Example 3 is the format to use for processing single days. The PRESSLE ICP tells the Pro-cessor to interpolate the input model levels to the specified pressure levels (in millibars).There will be one zonally averaged cross-section plot produced for each field, and seven

horizontal plots each for T and Q (on the 1000., 850., 700. ,500., 300., 200. and 100.millibar pressure levels).

The ICP ZONAVG = 'YES' requests that zonal averages are to be computed and plotted.ZAVGPRN = 'YES' prints the zonally averaged values of T and Q in the output. The globalaverage values are printed as well.

DPLTMF, the ICP which specifies where to send the plots at the end of the jobstep, is notspecified. Thus, by default, the plots produced by this example are sent to the microficheprinter at the end of the run.

13

CC Example 3. - oneday.sh - Process 1 day (10.) for Case A. (.00766 GAUS)CC TITLEA will appear as the title on printout results and on plots.C TAPESA calls for the MSS file /CSM/ccm2/414/hist/h0002.C DAYSA requests day number 10.C FIELDAi calls for fields T, temperature and Q, specific humidity.CTITLEA = 'Example 3. - oneday.sh - Process Day 10.0'TAPESA = '/CSM/ccm2/414/hist/h0002'DAYSA = 10.0FIELDA1 = 'T','Q'CC Invoke vertical interpolation from input model levels to theC specified pressure levels by use of the PRESSLE ICP.CPRESSLE = 1000.,850.,700.,500.,300.,200.,100.C

C Produce plots by using the horizontal projection option HPROJ.CHPROJ = 'RECT'CC Compute/plot (ZONAVG) and print (ZAVGPRN) the zonal averages.CZONA VG = 'YES'ZA VGPRN = 'YES'CENDOFDATA ----------------------------------------

Example 4. - 30-day-ave.sh - Produce a thirty-day time average.

The next job produces a thirty day time average for Case A, using do-loop notation to

specify the days list. Note, that if only one case is processed, Case A is used for case

dependent keywords. The HPROJ ICP generates 28 horizontal projection plots (4 fields x

7 pressure levels), while the ZONAVG ICP produces 4 zonal mean cross-section plots.

CC Example 4. - 30-day-ave.sh - Time average of 30 days. (.03295 GAUS)

CTITLEA =.'Example 4. - 30-day-ave. sh - 30 DAY AVG (Days 20-49) 'TAPESA = '/CSM/ccm2/414/hist/h0003'

CC NINTAPA automatically increments the input tape number when needed.C DAYSA list is in do-loop notation.C

NINTAPA = 3,4,1DAYSA = 20.0,49.0,1.0

CFIELDA1 = 'T','U','V',Q'PRESSLE = 1000.,850.,700.,500.,300.,200.,100.

CC Request time averaging.C

TIMAVGA = 'YES'CC Produce plots by using the horizontal projection option HPROJ.C

HPROJ = 'RECT'CC Set the scale factor for meridional cross-section plots of Q.C

MXSCAL = 'Q',1.E3CC Compute, plot and print the zonal averages, send to laser printer.C

ZONA VG = 'YES'ZAVGPRN = 'YES'DPLTMF = 'MP'

CSAVHSTA = '/USERNAME/ccm2/414/hist/example4'PWDHSTA = 'WRPASS'

CC BPHSTA = 'YES' allows blocked points to be written out.C SAVMHST specifies that the time averaged data should be written out.C

BPHSTA = 'YES'SAVMHST = 'TAV'

CENDOFDATA --------------------------------

14

_ _ _

Example 4 is the format for time averaging a series of model days. Here, the first input

Mass Store file is /CSM/ccm2/414/hist/h0003. NINTAPA automatically increments the

input tape number when the next input tape is needed. Here, NINTAPA = 3,4, 1 requests a

total of 3 tapes whose names are formed by numerically incrementing the last 4 characters

of the file specified by the ICP TAPESA by 1 when needed. The same effect could be

obtained by specifying the three tape names with the TAPESA ICP. Do-loop notation is

used for the DAYSA specification.

Time averaging of all the fields is specified via the TIMAVGA = 'YES' ICP. The only differ-

ence between processing of individual days and generating a time average of the individual

days is the value of TIMAVGA.

DPLTMF = 'MP' sends the plots of the time averaged data to the SCD laser printer.

The data is saved on a Mass Store file for future use by invoking the SAVHSTA keyword.

PWDHSTA assigns a write password to the MSS file.

The ICPs TIMAVGA = 'YES' and SAVMHST = 'TAV' are both required to ensure that only

the time averaged data is to be saved to the tape. The default for SAVMHST is 'TSR', whichwrites each individual time sample to the output tape, regardless of the value of TIMAVGA.

Figure 2 shows the second of 32 plots produced by this jobstep. Note the "masked" con-

tours where the 850 mb pressure surface intersects the ground in regions of high elevation.

CASE. 414 CASE 414 plx19Example 4. - 30-day-ave.sh - 30 DAY AVG (Days 20-49)

TIME AVERAGE FOR DAYS 20.0 TO 49.0 BY 1.0 T 850.OP180oW 150W 120W 90w 60W 30W 0 30E 60E 90E 120E 150E 180E

180W 150W 120W 90W b60 30W 0 30E - O

Contour from 240 to 295 by 5

90E 120E 150E 1 DE

Fig. 2. Time Average of T at 850 mb from 30-day-ave. sh.

15

Example 5. - compare-aves.sh - Produce and compare two ten-day averages

Example 5 uses the three-Case Capability to process the difference between two ten-day

averages from the CCM2 414 control run. Each ten-day average is processed in the same

manner as Example 4. The differences are requested for the field pass 1 fields by invoking

the DIFFLDi ICP. Eight plots are produced and disposed to the laser printer.

CC Example 5. - compare-aves.sh - Average and difference of 2 cases forC 10 model days. (.01761 GAUS)CC -- Specification of Case A -------- -------------------------C

TITLEA = 'Example 5. - compare-aves.sh - Case A: Average Days 30-39'TAPESA = '/CSM/ccm2/414/hist/h0004'DAYSA = 30.0,39.0,1.0FIELDA1 = 'T','U','VTIMAVGA = 'YES'

CC Save the time average of Case A to the MSS.C Note that SAVMHST applies to Cases B and C also.C

SAVHSTA = '/USERNAME/ccm2/414/hist/example5A'SAVMHST = 'TAV'

CC -- Specification of Case B ---------------- ….

CTITLEB = 'Example 5. - compare-aves.sh - Case B: Average Days 50-59'TAPESB = '/CSM/ccm2/414/hist/h0006'DAYSB = 50.0,59.0,1.0FIELDB1 = 'T','U','V'TIMAVGB = 'YES'

CC Save the time average of Case B to the MSS.C

SAVHSTB = '/USERNAME/ccm2/414/hist/example5B'CC -- Case C, compute A - B differences for for T and U only ---------C

DIFFLD1 = 'T','T' 'TDIFF', 'U ,U' 'UDIFF'

C Save the difference of time averages to MSS.C

SAVHSTC = '/USERNAME/ccm2/414/hist/example5C'C

ZONA VG = 'YES'DPLTMF = 'MP'

CENDOFDATA ----------------------------------

16

� __I_ __I�___ ______________

In Example 5, all averages are computed on the input model levels, since the PRESSLEkeyword is absent.

This example also introduces the concept of Cases. Each Case is a set of input datagrouped to allow comparisons with other Cases. The primary (control) Case is designated"Case A", and the secondary (experiment) Case is designated ""Case B". These twoCases may be quantitatively compared, and the result of such a comparison is designated""Case C". Alternatively, Case C may be created by merging Cases A and B. If neitherCase Comparison nor merging is requested, the data being processed should be designatedCase A. Some ICPs refer only to a specific Case, and are therefore characterized as being"Case dependent". An ICP is Case dependent if, and only if, the last alpha character ofthe associated keyword is an "A", "B", or "C". (The last alpha character may be followedby a numeric digit designating the "field pass" number.)

The keywords ending in 'A' are Case A keywords and those ending in 'B' are Case Bkeywords. These case-specific keywords only apply to that case. In this example, Case Aconsists of all the data associated with the day 30-39 time averages and Case B with thedata corresponding to the day 50-59 time averages.

The keywords ending in 'C' are Case C keywords. Case C always consists of either thedifference of Case A minus Case B, the ratio of Case A to Case B or the results ofmerging Case A and Case B. In this example, Case C is the difference (ratios canalso be computed in Case C, using the RATFLDn keyword). The differences of the time-

averaged Case A temperature field minus the time-averaged Case B temperature field arebeing computed and put in a field called 'TDIFF'. A similar computation is being donefor the u-wind field. The differences are then saved on a history save tape.

One important point to note about the DIFFLDn keyword is that it is a field pass spe-cific keyword. This means that the differences computed are for the specific field passreferred to in the keyword. For example, if FIELDA1='T' and FIELDB='U', then the ICPDIFFLD1='T' 'T', 'TDIFF' is invalid, because the 'T' field for Case B was not specifiedon the FIELDB1 ICP.

Figure 3 gives the index of plots produced by this jobstep.

FRAME PLOT DESCRIPTION FIELD LEVEL CASE DAY(S)

1.1 Time Avg. Zonal Avg. Ldt. Cross Section Contours T MULtIPLE A 30.0 TO 39.01.2 Time Avg. Zondl Avg. Lat. Cross Section Contours U MULTIPLE A 30.0 TO 39.01.3 Time Avg. Zonal Avg. Lat. Cross Section Contours V MULTIPLE A 30.0 TO 39.01.4 Time Avg. Zonal Avg. Lat. Cross Section Contours T MULTIPLE B 50.0 TO 59.01.5 Time Avg. Zonal Avg. Lat. Cross Section Contours U MULTIPLE B 50.0 TO 59.01.6 Time Avg. Zonal Avg. Lat. Cross Section Contours V - MULIPLE B 50.0 TO 59.01.7 Time Avg. Zonal Avg. Ldt. Cross Section Contours TDIFF MULTIPLE C 30.0 TO 39.01.8 lime Avg. Zonal Avg. Ldt. Cross Section Contours UDIFF MUL11PLE C 30.0 T10 9 1)

Fig. 3. Index of plots from compare-aves.sh.

17

Example 6. - rd-savetape.sh - Recompute differences and plots from two his-

tory save tapes

Example 6 computes the difference between data on two existing history save tapes.

/USERNAME/ccm2/414/hist/example5A and /USERNAME/ccm2/414/hist/example5B are

the two time-averaged history tapes that were created in Example 5. Example 6 pro-

duces exactly the same results as Example 5, except that the contour intervals for some

fields are specified explicitly, rather than selected automatically.

CC Example 6. - rd-savetape.sh - Recompute differences and plots of 2

C cases (A and B) for 10 model day average

C from previous saves of Case A and Case B.

C (.06043 GAUS)CC -- Specification of Case A by a time average history save tape -----

C The 10 model day average was saved in a previous Processor run

C (see Example 5). The TIMAVGA control parameter not required.

CTITLEA = 'Example 6. - rd-savetape.sh - Case A: Average Days 30-39'

TAPESA = '/USERNAME/ccm2/414/hist/example5A'FIELDA1 = 'T','U','V'DAYSA = -1.PRNTHD = 'FULL

CC -- Specification of Case B by a time average history save tape -------

CTITLEB = 'Example 6. - rd-savetape.sh - Case B: Average Days 61-69'

TAPESB = '/USERNAME/ccm2/414/hist/example5B'FIELDB1 = 'T','U','V'DAYSB = -1.

CC -- Case C, compute differences of T and U from cases A - B -------

CDIFFLD1 = 'T','T','TDIFF,'U','U',' UDIFF'

TITLEC = 'Example 6. - rd-savetape.sh - Case C: Difference Averages'

CC -- Produce plots for all cases --- …-- . ----------------CC Specify contour intervals for T,U, and V for meridional cross-section.

CZONAVG = 'YES'ZAVGPRN = 'YES'MXCINT = 'T',5.,'U',5.,'V',2.DPLTMF = 'MP'ENDOFDATA ------------------ -------------- _----------

18

- -- ~ ~ ~ ~~~~~~~~~~~~~~~--

I - - - - - - _

In example 6, both DAYSA and DAYSB are set to -1., which requests that the first day onthe tape be processed, regardless of what the day number actually is. Since only one day,the time average of days 30-38 for Case A and the time average of days 60-69 for Case B,was written to each tape in example 5, this is sufficient to input the data.

Manual selection of contour intervals is often desirable in order to generate more readableplots. Contour intervals for meridional cross-section plots are specified in pairs. Here,MXCINT'T' ,5. 'U' , 5. 'V' ,2. specifies that a 5 degree contour interval is selected forT, 5 m s - 1 for U, and 2 ms- 1 for V.

The PRNTHD = 'FULL' ICP prints out the complete history tape header for all input andoutput tapes. The header contains a description of the data on the history tape. Seesection I.C.2.a, Model History Tape on page 38 of the User's Guide to NCAR CCM2 foran explanation of the data contained in the history tape header.

The units of the fields can be found in the header information. If different units for a fieldare desired, a conversion may be performed via the DERFLD capability (see Example 11 onpage 28).

Figure 4 shows the first of eight plots produced by this jobstep.

CASE. 414 Example 5. - compare-aves.sh - Case A. Average Days 30-39Example 6. - rd-savetape.sh - Case A, Average Days 30-39

DAY 39.000 TZONAL AVERAGE FROM -180.O 10 177.2 DEGREES

35

25.0

15.0

10 0

5..

Contour fromi 185 to 300 by 510/26/2 21.43.20

Fig. 4. Zonal average of T from rd-savetape. sh.

19

Example 7. - plt-diffs.sh - Replot only differences from a save tape, respecifying

contour intervals

One use of save tapes is to save the condensed results of a previous run to allow them to

be replotted (for example, the default contour interval may not be adequate for a readable

plot of the difference, and it may be desirable to select one manually). Note the request

of the difference fields in the same manner as any other input field request.

The MSS file saved as Case C in example 5 can be read as Case A in another run. Fields

created and saved in one Processor run can be referred to in another run. In this example,

the contour intervals are different, and a scaling factor (HPSCAL) has been added to change

the labels of plots on the UDIFF field from m s- 1 to cm s - 1

Note that the values specified for contour intervals (HPCINT) and plot scaling (HPSCAL) are

applied to all levels above, and including, the indicated level. See the documentation for

HPCINT for more details.

20

CC Example 7. -plt-diffs.sh - Replot the differences from the Case C

C history tape created in example 5.

C (.02179 GAUS)CC The differences were saved in previous Processor run (see

C Example 5). The TIMAVGA control parameter is not required.

CTITLEA = 'Example 7. - plt-diffs.sh - Difference 10-day Averages'

TAPESA = '/USERNAME/ccm2/414/hist/exampleSC'DAYSA = -1.FIELDA1 = 'TDIFF', 'UDIFF'

CC Produce horizontal plots.C HPCINT: Specify contour intervals for horizontal plots for TDIFF.

C HPSCAL: Specify scale factor for U field.CHPROJ = 'RECT'HPCINT = 'TDIFF',1000.,1.HPSCAL = 'UDIFF',1000.,100.

CC Zonally average the data and plot it.C

C MXCINT: Specify contour intervals for meridional cross-section.

CZONA VG = 'YES'ZAVGPRN = 'YES'MXCINT = 'TDIFF',1.DPLTMF = 'MP'ENDOFDATA ---------------------------- .-----------

-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CASE, 414Example 7. - plt-diffs.sh - Difference 10-day Averages

30.000 TDIFFZONAL AVERAGE FROM -180.0 TO 177.2 DEGREES

35.0

25.0

20.0

15.0

10.0

5.0

Contour from -15 to 8 by 110/20/92 09.45.04

DAY

lil 16 Ii F I :1I, I' I, I I I d I II

.88X\''', , , ,

) \I, , ,:,, , , , v

a a, -·, v I .

i a

a , a a , a ,

I II %. Ka

I I I I

,, a

\ I-I 8

I I i I

IS e I I I ·

s i I i i i I

iI I

a a t I I a

I~~

' , ' ',, ' '· a, a

i

i i iI i I

i Ii i I

s /

i /i

sI I I % %·% I Ii t I ~ s

I Ii I i % 1,..t % ·

~~~~~~--A

I 1 b"I ·,,:,, . .

/iti I I \ '~.. ~i .,..

i ~ i , . " , ..s .' - -

; ..... .: i .:~

/ % , - ,.,, % .

i( ·

i .

" "r' L-li~8

' /

Frame 1.37

Fig. 5. Graphical output from plt-diffs.sh.

21

Example 8. - hsl.sh - Make and read a horizontal slice save tape.

Often the user may want to manipulate the data from outside of the Processor. Horizontal

slice save tapes are ideal for this. The output data format for horizontal slice save tapes is

very simple; flat longitude by latitude arrays for each field at each level. Example 8 shows

how to use the Processor to make a horizontal slice save tape for selected fields. The second

step shows how to use a FORTRAN program to read the data on the horizontal slice save

tape. Note that data points on pressure levels which extend below ground elevation are

flagged with values of 1.E36.

#!/bin/csh#QSUB -q prem -lt 10 -lT 13 -lm 2Mw -1M 2Mwcd $TMPDIRcat >! parms << 'END'CC Example 8. - hsl.sh - Write a Horizontal Slice Save tape (.00325 GAUS)CTAPESA = '/CSM/ccm2/414/hist/h0002'DAYSA = 12.FIELDAI = 'PHIS, 'T'PRESSLE = 500.,200.SAVHSLA = '/USERNAME/ccm2/414/hsl/example8'ENDOFDATA ------ ------------------------ -----'END '

/ccm/proc/Processor

cat >! rdhsl.f << 'EOFI'program rdhsl

cc hsl.sh Read data fc See the Proc Here, recorc a(1.1) is ac

II exit # run the Processor

rom a Horizontal Slice Save tape.cessor output for the specific data order.d 1 is PHIS, 2 is 500mb T, 3 is 200mb T.t 90S,180W, a(129,64) is at 90N,180E.

dimension a(129,64)do 10 i=1,3

read (11,end=99,iostat=ios) a ! Read 1 129x64 data recordwrite (6,*)i,a(1,1),a(20,20),a(129,64) ! Print out a few points

10 continuestop

99 write(6,*) 'EOF reading from unit 11, record= ',i,' iostat= ',iosstopend

'EOFI'cf77 -L/usr/local/lib -lncarg rdhsl.fmsread MKHSL.data /USERNAME/ccm2/414/hsl/example8assign -a MKHSL.data fort.11a.out # execute the FORTRANexit

II exitII exitII exit

22

_ _

__ __ i-- --- --

- 1% - IF - I - - -

Example 9. - std-dev.sh - Compute standard deviations from four save tapes..

Example 9 shows how to process time-average statistics for selected fields. TheSDFLDA1 ICP indicates that the point-wise standard deviation for the field T should becomputed. Note that this is a standard deviation of the previously computed time aver-ages.

A series of time averages can again be time averaged by specifying all the time averageson the TAPESA ICP. The standard deviations are one of the time-average statistics thatcan be computed. The standard deviation specification is an example of one of the manykeywords specified as pairs or triplets. The MSPFXIA ICP is used as the prefix for each ofthe files specified on the TAPESA ICP, producing /CSM/CCM1/223/STA01, etc.

An alternative method for specifying a list of input tape names is available via the NIN-

TAPc ICP. NINTAPc enables the automatic expansion for TAPESc lists which progressnumerically. Specifying:

TAPESA = '/CSM/CCM1/223/STA01'NINTAPA = 4,2,1

will request a total of 4 tapes where the last 2 characters of following tapes are increasedin increments of 1 based on the first tape having the name /CSM/CCM1/223/STA01.

23

CC Example 9. - st-dev.sh - Compute standard deviations from 4 save tapes.C (.01099 GAUS)CTITLEA = 'Example 6. - hsl.sh - Case A - Four 90 Day Averages '

CC Four 90 model day averages were saved in previous Processor run.CMSPFXIA = '/CSM/CCM1/223/'TAPESA = 'STAO1', 'STA02', 'STA03', 'STA04'TYPEA = 'SAVTAV

CFIELDAI = 'T'TIMAVGA = 'YES'

CC Compute standard deviation of T.C

SDFLDA1 = 'T','SDT-T'CC Produce horizontal and zonally averaged plots.C

HPROJ = 'RECT'ZONAVG = 'YES'ZAVGPRN = 'YES'

ENDOFDATA -----------------------------------------------

Example 10. - ave-ave.sh - Average two five-day time averages

Some tasks cannot be completed in one Processor jobstep. In this case, multiple sets

of ICPs can be combined as shown, to produce the desired result. In this example, the

composite average of two five-day time averages is computed by using three jobsteps.

CC Example 10. - ave-ave.sh - Create two five-day time averages, and

C average the results. (.01324 GAUS)CC -- JOBSTEP 1. Create the first time average --------- ---------

CC Time average for model dates Jan 05 0001 - Jan 09 0001.CTITLEA = 'Example 10.1 - ave-ave.sh - Time average - JOBSTEP 1'

TAPESA = '/CSM/ccm2/414/hist/h0013', '/CSM/ccm2/414/hist/h0014'DAYSA = 010105.0,010109.0,1.0DAYTYPA = 'DATE'FIELDAI = 'T'TIMAVGA = 'YES'

CC Create and plot a zonal average of the time average.CZONAVG = 'YES'SAVHSTA = '/USERNAME/ccm2/414/hist/examplel0.1'PWDHSTA = 'WRPASS'SAVMHST = 'TAV'

CC Don't dispose the plots yet.C Print the ICP list to the plot file.CDPLTMF = 'NO'ICPECHO = 'BOTH'

CC Each jobstep ends with a separate ENDOFDATA.CENDOFDATA --------------------------------------.CC -- JOBSTEP 2. Do same operations for second time average. ----CTITLEA = 'Example 10.2 - ave-ave.sh - Time average - JOBSTEP 2'

TAPESA = '/CSM/ccm2/414/hist/h0050','/CSM/ccm2/414/hist/h0051'TIMAVGA = 'YES'

CC Time average for model dates Jan 05 0002 - Jan 09 0002.CDAYSA = 020105.0,020109.0,1.0DAYTYPA = 'DATE'FIELDA1 = 'T'

- Continued on the next page -

24

-- ~~~ ~ ~~~ ~ ~~~ ~ ~~~ ~ ~~ ~ ~~ ~ ~~ ~~~ ~~~ ~~~ ~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I - I ~ -

Example 10 demonstrates that a more complicated task can be built from a series of simple

jobsteps. Each of the first two jobsteps creates a time average. The third jobstep computes

the time average of the first two. The ENSMBLA keyword specifies ensemble averaging of

the tapes /USERNAME/ccm2/414/hist/examplel0.1 and examplel0.2, when it is set to

the value CASE. This option allows averaging of multiple tapes with the same time values.

In the first two jobsteps, the DAYTYPA = 'DATE' ICP indicates DAYSA are dates, rather

than model days. In the third jobstep, flag values of -1. and -2. are used for DAYSA. See

the description of the DAYSA ICP formore details.

ICPECHO = 'BOTH' requests that a copy of all the ICP's for that jobstep be printed both

to the printed output and as the first frame of the plot file. The DPLTMF = 'NO' in the

first two jobsteps keeps the individual plot files from being disposed at the end of those

jobsteps. In the last jobstep, DPLTMF is not specified and, hence, all the plots for the threejobsteps will be disposed to the default output device, the Dicomed microfiche printer.

In jobstep 3, MSPFXIA is used to set a common input MSS pathname prefix for a list of

MSS filenames specified by TAPESA.

25

CZONA VG = 'YES'SAVHSTA = '/USERNAME/ccm2/414/hist/examplelO. 2'PWDHSTA = 'WRPASS'SAVMHST = 'TAV'

CC Don't dispose the plots yet.C

DPLTMF = 'NO'ICPECHO = 'BOTH'

CENDOFDATA -----------------------------------------CC -- JOBSTEP 3. Time average of the two save tapes. - ---------C

TITLEA = 'Example 10.3 - ave-ave.sh - Time average of 2 time averages'MSPFXIA = '/USERNAME/ccm2/414/hist/'TAPESA = 'examplelO.1', 'examplelO.2'DAYSA = -1.,-2.FIELDA1 = 'T'TIMA VGA = 'YES'ENSMBLA = 'CASE'ICPECHO = 'BOTH'

CZONAVG = 'YES'ZAVGPRN = 'YES'

CENDOFDATA -----------------------------------------------

Example 11. - derfld.sh - Create a simple user-defined derived field.

A powerful feature of the Processor is the ability to create user defined fields from either

the existing fields on the model history tapes or the set of Processor derived fields.

The DERFLD ICP defines a new field 'PRECmm/d', which is precipitation in millimeters per

day. This derived field uses the Processor derived field 'PRECT', which is the sum of the

model variable 'PRECC' (convective precipitation) and 'PRECL' (large-scale precipitation)

and multiplies it by 8.64E7 to convert the units from meters per second to millimeters per

day. Only the field being created by DERFLD needs to be requested in the FIELDA1. The

component fields used to make the derived field 'PRECT', 'PRECC', and 'PRECL' are not

requested in the FIELDA1 ICP. See Section 3.4 on page 49 for more details on DERFLD.

HPRBNDS defines the western, eastern, southern and northern boundaries for the horizontal

rectangular plots. HPPTVAL = 'BOTH' specifies that all horizontal projection plots are to

be plotted as both numeric point-values and contours, on separate frames

In this example, the DERFLD keyword also provides an example of an ICP which spans

more than one line. Note the leading comma on the second line of the ICP specification.

26

CC Example 11. - derfld.sh - Create a simple user-defined derived field.

C (.00386 GAUS)CC First, input an existing T42 dataset.CTITLEA = 'Example 11. - derfld.sh - Create a derived field.'

TAPESA = '/CSM/ccm2/414/hist/h0002'DAYSA = -1.CC Request only the derived field in the FIELDA1 ICP, not it's components.

CFIELDA1 = 'PRECmm/d'DERFLD = 'PRECmm/d',111,0,1,0

,Ps 'PRECT',8.64E7, ':TIMES', '.END'CC Plot the derived field.CHPROJ = 'RECT'HPRBNDS = -180.,0.,-20.,70.HPCINT = 'PRECmm/d', 1000., 0.HPPTVAL = 'BOTH'CC Dispose the plots back to a local NCAR computer.CDPLTMF = 'IS'DPLTRCPP= 'sun.cgd. ucar.edu:/d2/mydirectory/derfld.plt'CENDOFDATA ----------------------------------......

- -- --

I

Example 12. - spectral.sh - Spectrally truncate a T42 dataset.

The Processor has the capability to carry out a number of spectral operations. Thisexample creates a T5 dataset by spectrally truncating a dataset. In this example, theinput dataset is a T42 history tape from the CCM2 414 control run.

The SPCA1 ICP requests spectral processing and the SPCINTA ICP requests that the databe interpolated to a triangular 5 truncation.

The five values in the SPCINTA ICP correspond to:

1. New value for spectral truncation parameter M2. New value for spectral truncation parameter N3. New value for spectral truncation parameter K

4. New value for the number of longitude points (including two overlap points) in gridpoint space.

5. New value for the number of latitude points in grid point space.

The spectral operations used in the CCM are outlined in the document: Description of

NCAR Community Climate Model (NCAR/TN-285+STR). Also see the section covering

spectral interpolation in the CCM Processor Users' Guide for more information.

27

CC Example 12. - spectral.sh - Spectrally truncate a T42 dataset.C (.00398 GAUS)CC First, input an existing T42 dataset.CTITLEA = 'Example 12. - spectral.sh - Create a T5 dataset.'TAPESA = '/CSM/ccm2/414/hist/h0002'DAYSA = -1.FIELDA1 = 'T', 'U', 'V' 'Q', 'PHIS'CC Request spectral processing.C

SPCA1 = 'YES'CC Interpolate the data to a triangular 5 truncation.C

SPCINTA = 5,5,5,18,8CC Write the truncated data to the MSS with write password 'WRPASS'.CSAVHSTA = '/USERNAME/ccm2/414/hist/examplel2'PWDHSTA = 'WRPASS'CENDOFDATA ------------------------------------------------

3.2 A Brief List of Processor options

The following is a summary of some of the available keywords for each 'category' of

Processor function. Case dependent ICPs have a 'c' suffix, with the cases for which it is

valid listed in parentheses. The 'n' suffix indicates a field-pass dependent keyword. Refer

to the Processor Users' Guide for a complete description of the various ICP's and use of

each keyword.

There are four major divisions of the ICPs for the following tables. These four divi-

sions are further divided by processing function. These categories are:

A. DATA INPUT OPTIONSA.1 Input Data Specification

A.2 LSD Driver

A.3 Input Data ModificationA.4 History Tape Input Data Limiting

A.5 Mass Store File Input

A.6 User Defined Derived Fields

B. PROCESSING OPTIONS

B.1 Case Comparison/Merging

B.2 Color PlottingB.3 Horizontal Plotting

B.4 Spatial Averaging

B.5 Spectral Processing

B.6 Time Average Statistics

B.7 Time Average Zonal Statistics

B.8 Time Filtering

B.9 Time Series Plots

B.10 Vertical Cross-Section Plotting

C. DATA OUTPUT OPTIONSC.1 Field Value PrintingC.2 Plot Disposition

C.3 Mass Store File Output

C.4 Save Tape Production

D. MISCELLANEOUS OPTIONS

D.1 Dataset Management

D.2 Memory Management

D.3 Miscellaneous Plotting

For each specific category listed above, in order, there follows a table of the keyword

name, possibly with a 'c' or 'n' suffix (see above), a brief description of the purpose of

the keyword, and an example of its use. Keywords new to this version of the Processor

(since the previous version of this document) are indicated by a superscripted asterisk (e.g.

KEYWORD*) in the Option column for that keyword. The (A,B) under purpose indicates

the keyword is valid for cases A and B only.

28

A. DATA INPUT OPTIONS

29

A.1 Input Data Specification

Option Purpose Example

TAPESc input tapes list (A,B) TAPESA='VSNOOA'

NINTAPc* Automatic TAPESc names NINTAPA=3,2

DAYSc list of days to process (A,B) DAYSA=10.

DAYTYPc interpretion for DAYSc value DAYTYPA='RELATIVE'

DLDAYSc* "do-loop" notation for DAYSc DLDAYSA=0.,3., 1., 5,9,1.

LEAPY* Leap year use flag LEAPY='YES'

FIELDcn list of fields to process FIELDA='T', 'U'

TYPEc type of input tape (A,B) TYPEA='CCM1'

TITLEc title for plots and printout TITLEA='A TITLE'

PRNTHD* print input headers PRNTHD=' PART'

A.2 LSD Driver


DRVRTYP specifies code driver to use DRVRTYP='LSD1'

NSBTAPc alternate list of partial Mass NSBTAPA='FILEfA','. END',Store Path Names for input tapes 'FILE2A','.END'

NSBDAYc alternate list of days to process NSBDAYA=0.0,1.0,.5,'.END',1.0,1.5,2.0,'.END'

PKLSlc LSD Save Tapes npacking density PKLS1A=4

PWLSlc MSS write password and PWLS1='MYPASS', 'CTPUBLIC'virtual volume name

RTLSlc flag used to determine the RTLS1A=5order of records

SAVLSlc list of MSS full or partial SVLS1A='TAPE1'pathnames for outputLSD Save Tapes

TITLSlc LSD Save Tape mini-header title TITLS1A='A title'

A.3 Input Data Modification


ENSMBLc option to process' as an ensemble ENSMBLA='CASE'the same day from multipleinput tapes (A,B)

MASKSc mask the input data according MASKSA='LAND', SICE'to the surface type flags (A,B)

TIMAVGc option to time average input (A,B) TIMAVGA='YES'

Vertical interpolation to pressure surfaces

INTDP set default interpolation type code INTDP=2

LBTDP default lower boundary treatment code LBTDP=4

NLCDP default number of planetary boundary NLCDP=Olayer levels to copy

PINTXL interpolation exceptions list PINTXL= HT1',2,1,0

PRESSLE pressure surfaces to interpolate to (mb) PRESSLE=1000.,850.,700.,...

Vertical interpolation to potential temperature surfaces

INTDT set default interpolation type code INTDT=2

LBTDT default lower boundary treatment code LBTDT=4

NLCDT default number of planetary boundary NLCDT=Olayer levels to copy

TINTMLT flag to indicate how multiple occurrences TINTMLT='BLOCK'of a given potential temperaturesurface are handled

TINTXL interpolation exceptions list TINTXL='HT1',2,1,0

TEMPLEV analogous to PRESSLE except that TEMPLEV=300.,list is potential temperature surfaces 280., 260.,..in degrees K

Use of Hybrid Sigma-Pressure surfaces

HYBASGc* manual hybrid processing switch HYBASGA='NO'

HYPRBc* base pressure HYPRBA=1000.

30

A.4 History Tape Input Data Limiting

A.5 Mass Store File Input


MSPFXI case-independent Mass Store Path MSPFXI='/CSM/CCM1/999/'Name prefix for input datasets

MSPFXIc case-dependent Mass Store Path MSPFXIA='/CSM/CCM1/999/'Name prefix for input datasets

MSTXTI case-independent text string for MSTXTI=20HKEYWORD='value'Mass Store input datasets

MSTSTIc case-dependent text string for MSTXTIA=20HKEYWORD='value'Mass Store input datasets

PDNIDI case-independent ID to use on PDNIDI='PDNID'ACQUIRE for input datasets

PDNIDIc case-dependent ID to use on PDNIDIA='PDNID'ACQUIRE for input datasets

A.6 User-Defined Derived Fields

Option Purpose ' Example

DERFLD define a new field DERFLD='TCELS',61,2,3,0,'T',273.15,':MINUS','END'

FLDSRCc determines how to resolve FLDSRC='INPUT'ambiguities if the derivedfield name conflicts with aninput field name (A,B)

UNDEFDF* code-defined derived UNDEFDF='PRECT'fields to be undefined.

31


DEFLDcn explicit field deletion list DEFLDA='T' ,61

SIGLEVc option to limit the sigma processed (A,B) SIGLEVA=1,4,5

SURFLEV option to exclude the surface level SURFLEV='NO'

SUBPc option to limit input pressure levels (A,B) SUBPA=1,4,5

LYRSUBc* general level limiter (A,B) LYRSUBA=3,4,6

I

B. PROCESSING OPTIONS

32

B.1 Case Comparison/Merging


ABMERGE controls merging of cases A and B ABMERGE='YES'to form case C

ORIGFLD option to continue processing ORIGFLD='NO'original fieldsafter doing case comparison

DIFFLDn list of difference fields to process DIFFLD='T','T', 'T-DIFF'

RATFLDn list of ratio fields to process RATFLD= 'T','T', 'T-RATIO'

B.2 Color Plotting


CLCNTNT color of continental outlines CLCNTNT='001'

CLCTRGE color of contours > dividing value CLCTRGE='001'

CLCTRLT color of contours < dividing value CLCTRLT='001'

CLLABEL color of plot labels and borders CLLABEL='001'

CLHIGHS color of marked highs CLHIGHS='001'

CLLOWS color of marked lows CLLOWS='OO1'

CLPNTVL color of point values plotted CLPNTVL='001'

CLVLTD color of vectors < dividing value CLVLTD='001'

CLVGED color of vectors > dividing value CLVGED='001'

COLOR* automatic coloring COLOR='YES'

CLBACK* set background/foreground colors CLBACK=' BONW'

CLTABLE* set individual color table values CLTABLE=1.,1.,0.,0.

I

B.3 Horizontal Plotting

Option

HPROJ

HEMIS

HPCINT

DASHLIN

HPCDIV

HPPTVAL

HPSCAL

HPLFPVn

HPVOPT

HPVSCAL

HPVDIN

HPVDIV

HPRADP*

HPRASPR*

HPRSIZE*

HPMCINT*

HPCNWKR*

HPCNWKI*

HPSMTH*

HPSMTHSL*

HPDTCNT*

CONLABS*

CONLABB*

Purpose

horizontal plot projection

hemispheric plot option

contour interval specification

option to dash some contours

contour dividing value

option to print values on plots

scale factor for plot contour labels

field pairs to be plotted as vectors

vector plot option for HPLFPVn

scale factor for horiz. vector plots

vector density plotting increment

vector dividing value (colors only)

Radius of polar plots in degrees

rectangular plot aspect ratio

rectangular plot size

set irregular contour intervals

set CONPAK real work array

set CONPAK integer work array

request spline smoothing

spline smoothing distance

dot the continental outlines

density of contour level labels

set boxing of Highs and Lows

Example

HPROJ='POLAR'

HEMIS='NORTH'

HPCINT='T',500.,10.

DASHLIN='YES'

HPCDIV='T',500.,240.

HPPTVAL='BOTH'

HPSCAL='T',500.,100.

HPLFPV1='U','V','WIND'

HPVOPT='VECT'

HPVSCAL='WIND',500.,20.

HPVDIN=1

HPVDIV='U','V','WIND'

HPRADP=40.

HPRASPR=1.1

HPRSIZE=0.8

See documentation

HPCNWKR=5000.

HPCNWKI=2000.

HPSMTH=-1.O

HPSMTHSL=0.01

HPDTCNT=1

CONLABS=2

CONLABB=2

Limited Area Horizontal Plots

HPRBNDS rectangular plot boundaries HPRBND=-180.,60.,10. ,90.

HPRNDIV number of plot divisions HPRNDIV=2

33

Ii I

.. . .I

L

t

B.4 Spatial Averaging


MERAVG meridional averaging options MERAVG='YES'

MAVGDSP disposition of meridional averages MAVGDSP='PLTPROC'

MAVGPRN option to print meridional averages MAVGPRN='YES'

MAVRNG range of latitudes for meridional average MAVRNG=-45.,45.

MBKFR blocking fraction for valid meridional avg. MBKFR=.1

VERAVG vertical averaging option VERAVG='YES'

VAVGDSP disposition of vertical average data VAVGDSP='PROC'

VAVRNG vertical averaging range VAVRNG=1000.,600.

VBKFR blocking fraction for valid vertical avg. VBKFR=.01

ZONAVG zonal averaging option ZONAVG='YES'

ZAVGDSP disposition of zonal average data ZAVGDSP='PLTPROC'

ZAVGPRN option to print zonal averages ZAVGPRN='YES'

ZAVRNG range of longitudes for zonal average ZAVRNG=-145.,145.

ZBKFR blocking fraction for valid zonal average ZBKFR=. 1

MSKFLcn masked area average specification (A,B) MSKFLA1='T' 'TM''LAND','OCEAN',15.,75.,-135,,60.

MSKAP determines if ordinary MSKAP=' NO'masked area averages are computed

MSKAPS determines if the masked area MSKAPS NO'average of the squares is computed

MSKAZS option to compute the masked area MSKAZS'NO'average of squares of zonal averages

SFCTTAP name of surface type save tape to read SFCTTAP='SR15JA'

SFCTCRT name of surface type save tape to create SFCTCRT='SR15JA'

34

_ _____ __

I

i

35

B.5 Spectral Processing


SPCINTc changes horizontal resolution (A,B) SPCINTA=15,15,30,50,40

SPCMNKc spectral transformation parameters SPCMNKA=15,15,30to use when transforming gridpointdata into spectral space

SPSNGRF controls spectral graphics SPSNGRF='YES'

SPGYINT controls y-interval range on SPGYINT=1.E4spectral graphs

SPCcn controls spectral processing (A,B) SPCA1='YES'

SPCBPcn sets range of spectral SPCBPA1=0,5,1,6bandpassing (A,B)

SPCDFcn indicates fields to be deleted before SPCDFA1='T', ''return to gridpoint space (A,B)

SPCEFcn fields to be excluded from SPCEFA1='T'spectral processing (A,B)

SPCVP defines fields as vector pairs for SPCVP='TAUX','TAUY',purpose of computing vector pair 'DIV-TAU', 'VOR-TAU',derived fields in spectral ' CHI-TAU',' PSI-TAU',

'UD-TAU','UZ-TAU''VD-TAU','VZ-TAU'

SPCTAVV* controls spectral data form SPCTAVV='NRMSHC'

B.6 Time Average Statistics

B.7 Time Average Zonal Statistics


ZSTFLcn time average zonal standard ZSTFLA1='T , 'T-ZSDV'deviations (A,B)

ZCVFLcn time average zonal standard ZCVFLA1='U', 'V ,'T-CVFL'covariances (A,B)

B.8 Time Filtering


TIMFILc time filtering option (A,B) TIMFLA='LOWP'

TFWTSc array of filtering weights to use (A,B) TFWTSA=-., 1.

36


CVFLDcn list of covariance fields CVFLD='U' ,'V', UV-COVR'to compute (A,B)

SDFLDcn list of standard deviation fields SDFLD='T','STD-T'to compute (A,B)

TCFLDcn list of total eddy covariance fields TCFLDA1='U ,'V','TCVR-UV'

to compute (A,B)

PRFLDcn list of product fields PRFLDA1='U, 'V, PROD-UV )

to compute (A,B)1

B.9 Time Series Plots

Option

SAVTSPR

SATSPW

TSPZLcn

TSPALcn

TSPPLcn

TSPZCcn

TSPMCcn

TSPFNPn

TSPFPH

TSLPASP

TSLPSIZ

TSZCASP

TSZCSIZ

TSMCASP

TSMCSIZ

CLTSLPc

TSPDYSc*

TSPMCLR*

TSPZCLR*

TSPYSCL*

Purpose

time series plot save tape to be read

time series plot save tape to be written

zonal average time seriesline plots

masked area average time series line plots

time vs. field value line plots

time vs. zonal average contour plots

time vs. meridional average contour plots

line plot pairing option (A,B)

specification for handling TSPFNPn

aspect ratio for time series line plots

size fraction for time series line plots

aspect ratio for zonal average contourtime series plots

size fraction for zonal average contourtime series plots

aspect ratio for meridional averagecontour time series plots

size fraction for meridional averagecontour time series plots

color of time series plot lines

time series renumbering option

longitude range for long-time plots

latitude range for time-lat plots

y scaling for time series line plots

Example

SAVTSPR='VSNTSP'

SATSPW='VSNTAP'

TSPZLA1='U',500.,45.,0.,0.

see Users Guide

TSPPLA1='Z',500.,82.,-62.,0.,0.

TSPZCA1='T',500.,0.,0.,0.

TSPMCA1='T',500.,O0.,0.,0.

TSPFNP1='T'

TSPFPH='BOTH'

TSLPASP=.7

TSLPSIZ=.75

TSZCASP=.7

TSZCSIZ=.75

TSMCASP=.7

TSMCSIZ=.75

CLTSLPA='001'

TSPDYSA=0.,1.

TSPMCLR=-130.,-70.

TSPZCLR=-20.,20.

TSPYSCL='LIN'

37

I

B.10 Vertical Cross-Section Plotting


LMLFPSL

LXASPRT

LXCINT

LXCDIV

LXLNSCL

LXLNRNG*

LXSCAL

LXSIZE

LXPTVAL

MXASPRT

MXCDIV

MXCINT

MXLNSCL

MXLTRNG

MXSCAL

MXSIZE

MXPTVAL

MXPLOT

LXPLOT

ZORD

list of multilevel fields to plot assingle levels

lat. x-section plot aspect ratio

lat. x-section plot contour interval

lat. x-section plot dividing value

lat. x-section plot logarithmic scale option

Ion range for x-section plots

lat. x-section plot scale factor

lat. x-section plot fractional size

option to print point values onlatitudinal x-section plots

aspect ratio of meridional x-section plot

meridional x-section plot contourinterval dividing value

meridional x-section plot contour interval

meridional x-section plot logarithmicscale option

lat. range for meridional cross-section plots

meridional x-section plot scale factor

fractional size of meridional x-section plot

option to print point values on meridionalx-section plots

option to explicitly plot all availablemeridional cross-sections

option to explicitly plot all availablelatitudinal cross-sections

controls the addition of a height scale onall vertical cross-section plots

LMLFPSL='T'

LXASPRT=.7

LXCINT='T',10.

LXCDIV='T',240.

LXLNSCL='YES'

LXLNRNG=-130.,-70.

LXSCAL='U',100.

LXSIZE=.75

LXPTVAL-'BOTH'

MXASPRT=.7

MXCDIV='T',240.

MXCINT='U',100.

MXLNSCL='YES'

MXLTRNG=-90.,90.

MXSCAL='Q',1.E8

MXSIZE=.75

MXPTVAL='BOTH'

MXPLOT='YES'

LXPLOT='YES'

ZORD='YES'

38

-

II

i. .

I - - - I .. .. .L Li

C. DATA OUTPUT OPTIONS

39

C.1 Field Value Printing


PRINTc field printing switch PRINTA='YES'

PRFNMc list of fields to print PRFNMA='T'

PRLATc list of latitudes to print PRLATA=0.,10.

PRLONc list of longitudes to print PRLONA=-60.,170.

PRLEVc list of levels to print PRLEVA=850.,500.

PRLIMR limiting range of values for printing PRLIMR=280.,300.

NSDPRNT number of significant digits NSDPRNT=8to compare for case comparison

B.2 Plot Disposition


DPLTCA specifies DICOMED camera to use for each DPLTCA='FICHE'corresponding value of DPLTMF

DPLTRCP* Remote host for plot disposition see online help

DPLTCP* Local filename to copy plot file see online help

DPLTCT specifies default processor case title to use DPLTCT='A'for DICOMED plot title

DPLTFN file name to use for dispose of a plot file DPLTFN='PLOTS'

DPLTIT file type to use for dispose of a plot file DPLTIT='METACODE'

DPLTIT DICOMED output plot title DPLTIT='Test Title'

DPLTMF name(s) of Network node for plot disposition DPLTMF='Dl' ,'IO0'

DPLTXT character string to append to text DPLTXT='USER=OTHER'field for plot file DISPOSE

MNFRMS minimum number of frames produced per MNFRMS=10000dispose group

MXFRMS maximum number of frames produced per MXFRMS=10000dispose group

I

40

B.3 Mass Store File Output


MSPFXO case-independent Mass Store Path MSPFXO='/MYNAME/SAVTAV/'Name for output datasets

MSPFXOc case-dependent Mass Store Path MSPFXOA='/MYNAME/SAVTAB/'Name for output datasets

MSTXTO case-independent text string for MSTXTO=20HKEYWORD='value'Mass Store output datasets

MSTXTOc case-dependent text string for MSTXTOA=20HKEYWORD='value'Mass Store output datasets

MSRTO case-independent Mass Store dataset MSRTO=' 365'Retention Time

MSRTOc case-dependent Mass Store Dataset MSRTOc='365'Retention Time

PDNIDO case-independent ID to use on SAVE PDNIDO='PDNID'for output datasets

PDNIDOc case-dependent ID to use on SAVE PDNIDOA='PDNID'for output datasets

B.4 Save Tape Production


History Save Tapes

SAVHSTc output a History Save Tape SAVHST='TAPE1'

SAVMHST mode flag for History Save Tapes SAVMHST='TAV'

NSVHSTc* auto-expand the SAVHSTc list NSVHSTA=3

BPHSTc option to write blocked points BPHSTA='YES'

OFTHSTc format for output history tapes OFTHSTA='CCM1'

PKHSTc packing density (A,B) PKHSTA=1

PWDHSTc write password, and Mass Store PWDHSTA='PASSWD'virtual volume for all history save tapes

NDYHSTc maximum number of days to put NDYHSTA=30on a single history tape (A,B)

Time Average Save Tapes

SAVTAVc output time average save tape SAVTAVA='VSNOO1'specification

Time Series Save Tapes

SAVTSRc output time series save tape list SAVTSRA='VSNTSR'

NSVTSRc auto-expand the SAVTSRc list NSVTSRA=3

NDYTSRc maximum number of days for each NDYTSRA=60time series tape

PWDTSRc write password for time PWDTSRA='MYPASS'series tapes

SAVMTSR mode flag for output of Time Series SAVMTSR='TAV'Save Tapes

Horizontal Slice Save Tapes

SAVHSLc output a horizontal slice save tape SAVHSLA='VSNHSL'

SHSLZAV option to put zonal average values SHSLZAV='YES'on the horizontal slice save tape

SAVMHSL mode flag for output horizontal SAVMHSL='TAV'slice Save Tapes

41

D. MISCELLANEOUS OPTIONS

D.2 Memory Management Options


MEMORY no. of words of memory to preallocate MEMORY=200000

MEMCON memory conservation option MEMCON='YES'

D.3 Miscellaneous Plotting Options


INDEX controls production of the plot index INDEX='PRINT'

NUMPLT controls whether or not a frame numberis printed at the bottom of each plot NUMPLT='YES'

PTOPc pressure at the top of the model, used for PTOPA=O.computing code-defined derived field DELPRES

42

D.1 Dataset Management Options


DELREL controls disposition of input permanent DELREL=1datasets once they have been read

DELPDN list of permanent disk datasets to delete DELPDN='VSN001'_ . .________. _ - - , - - -- ^ - - - - ^ - - - - - - - ^ I

3.3 List of Fields Available for Processing

There are a wide variety of fields output by the CCM, and it is necessary to know theproper identifier for each field name. This table lists the default fields output by CCM2,according to its field name, number of levels (1=single level, n=multilevel), the variableit represents and its units. For more detail about these fields see the Users' Guide to theNCAR CCM2 (Bath et al. 1992).

DescriptionLevel Units~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CCM2 Model Variables

N

PHISPSTUVQTA01VD01DC01DTHORO

WETSNOWHPRECLPRECCSHFLXLHFLXQFLXPBLHUSTARTPERTQPERTDTV

11nnnnnnnn

1

11111111111n

surface geopotential (instantaneous)surface pressuretemperaturezonal wind componentmeridional wind componentspecific humidityQ advective tendencyQ vertical diffusive tendencyQ convective adjustment tendencyT horizontal diffusionsurface type (instantaneous)

soil moistureliquid water equivalent snow depthlarge-scale,- stable precipitationconvective precipitationsurface sensible heat fluxsurface latent heat fluxsurface water fluxplanetary boundary layer heightsurface friction velocityPBL plume T perturbationsPBL plume Q perturbationsT vertical diffusion tendency

m2/s2

PaKm/sm/sKg/KgKg/(Kg-s)Kg/(Kg.s)Kg/(Kg-s)K/s0=ocean1=land2=sea icemmn/s

m/sW/m 2

W/m2

Kg/m 2 /smm/sKKg/KgK/s

43

Field

123456789

1011

121314151617282920212223

Level Units

.I II I I


Field

FSNSFLNSFLNTFSNTCLOUDEFFCLDFLNTCFSNTCFLNSCFSNSCOMEGADQPTAUXTAUYSRFRADQRSQRLCLDTOTCLDLOWCLDMEDCLDHGHTS1TS2TS3TS4SOLINUTGWVTGWTAUGWXTAUGWYDTCONDCMFDTCMFDQCMFMCCMFSLCMFLQCNVCLD

Level

1111nn1111nn111n

111111111nn11nnnnnn1

Description

net downward solar flux at sfcnet upward longwave flux at sfcnet downward longwave flux at topnet upward solar e flux at topfractional cloud covereffective cloud covernet clear sky longwave upward flux at topnet clear sky solar downward flux at topnet clear sky longwave upward flux at sfcnet clear sky solar downward flux at sfcvertical pressure velocityQ tendency from precipitationzonal surface stressmeridional surface stressradiative flux absorbed by sfcsolar heating ratelongwave heating ratetotal cloud fraction (random overlap)low cloud fraction (random overlapmedium cloud fraction (random overlaphigh cloud fraction (random overlapsurface temperature (level 1)subsurface temperature (level 2)subsurface temperature (level 3)subsurface temperature (level 4)solar insolationU tendency from gravity wave dragV tendency from gravity wave dragE/W sfc stress from GWD schemeN/S sfc stress from GWD schemeT tendency from convective adjustmentT tendency from convective parameterizationQ tendency from convective parameterizationtotal convective mass fluxconvective liquid water static energy fluxconvective total water energy fluxconvective cloud fraction

44

N

24252627282930313233343536373839404142434445464748495051525354555657585960

I . I I - -

I

Additionally, many derived fields are available. These fields are requested in the

same manner as fields output directly from the model. The versions column indicateswhich version of the model (2=CCM2, 1=CCM1 or 0=CCMOB) the derived field is valid.

These are the derived fields currently available from the Processor when processing historytapes:

Processor Derived Fields from CCM Variables

Field

CHICONDHDELPRESDIVDKEDLNPSXDLNPSYDVMAGENETENETSENETTHTOHT1KEKTOOPVOKTOOPV1LNPSMQNRADSPRECTPRESPSIPSLQSRCRADDRELHUMSIGDOTFSIGDOTHTCLD

Level

nnnnn11n111nnnnn1n11nn11nnnn1

Description

velocity potentialcondensational heating ratepressure layer thicknesshorizontal wind divergencekinetic energy of differencesx-derivative of natural log of surface pressurey-derivative of natural log of surface pressurevelocity magnitude of differencesnet total atmospheric energy fluxnet surface energy fluxnet top of Model energy fluxCCMOB geopotential height, full levels,CCM1 geopotential height, full levels,kinetic energyCCMOB kappa*temperature*omega/pressure

CCM1 kappa*temperature*omega/pressurenatural log of surface pressurewater vapor mass (3-dimensional)net radiative energy flux into surfacetotal precipitation (m for CCMOB)pressure on sigma surfacesstream functionsea-level pressuremoisture source termnet radiation (QRS+QRL) x 86400relative humiditysigma vertical velocity at full Model levelssigma vertical velocity at half Model levelstotal cloud fraction

45

Units

m 2 s-

K * dy- 1

Pas-1

J -kg- 1

Pa m- 1

Pa . m--1m s

W. m- 2

W-m- 2

W * m- 2

mm

2 -2m 2 s-

K · s- 1

K . s- 1

£n(Pa)Kg. m- 2

W * m- 2

m/sPam 2 s- 1

PaKg. m-2

K · dy- 1

percents- 1ss- 1

fraction

Versior

21010

210210210210210210

0000

1

01

210210

10210210210210

0210210

1010

210

O

L�� .

Processor Derived Fields from CCM Variables

Field

TESTTHETATMODKTMQTVUDUVSQUVSQDUVSQRUZVADVGV1VADVTVOVADVTV1VADVQVOVADVQV1VADVUV1VADVVV1VARWVVDVIKEVIPEVITEVMAGVORVZzZ2

Level

nnn1nnnnnnnnnnnnnnn111nnnnn

Description

3-D sinusoidal test fieldpotential temperature on sigma surfacestemperature used KTOOPV1water vapor mass in a column (2-D)virtual temperatureu-velocity computed from divergence alonetotal kinetic energy spectrakinetic energy spectra (divergent part)kinetic energy spectra (rotational part)u-velocity computed from vorticity alonevertical advection of a fieldvertical advection of CCMOB temperature,vertical advection of CCM1 temperature,vertical advection of Q, CCMOB versionvertical advection of Q, CCM1 versionvertical advection of U, CCM1 versionvertical advection of V, CCM1 versionkinetic energy variancev-velocity computed from divergence alonevertical integral of kinetic energyvertical integral of potential energyvertical integral of total energymagnitude of horizontal windhorizontal wind vorticityv-velocity computed from vorticity alonegeopotential heightgeopotential height for CCM2

Units

KKKg m- 2

Km sJ Kg- 1

J Kg-J * Kg-lm 5~--1

s-1K * s-1

K.s- 1

Kg. Kg-l s-Kg Kg- 1. s- 1

--2m's-2m * sm e s- 2

J * Kg-lm s 1

J m- 2

J *m- 2

J *m-2m~sm -1s-m *s-1

mm

You should consult the Processor Users' Guide before requesting any derivedfields. It is necessary to understand when each field is derived, and many derived fields

are not available when processing save tapes. Other derived fields can either be produced

by some code modification on your part, or by the use of user-defined derived fields.

46

Versior

2222222222

11111111111

00

000000000

TO

TO

TO

TO

TO

TO

TO

TO

TO

TO

10

111111111111

22

222

000000000

2- . . I --- --- -- I I

This table lists the fields output by CCM1. For more detail about these fields see themodel Users' Guide (Bath et al. 1987), and the Description of CCM1 (Williamson et al.1987).


Description

surface geopotentialsurface pressuretemperatureeast component of windnorth component of windspecific humidityu horizontal diffusive heating ratev horizontal diffusive heating rateT horizontal diffusionq horizontal diffusionsurface type = 0. for ocean

= 1. for land= 2. for sea ice

surface temperaturesurface wetnesssnow amountlarge-scale stable precipitationconvective precipitationlarge-scale stable snowfallconvective snowfallsoil moisture runoffsensible heat flux ratelatent heat flux rateheating from east-west surface stressheating from north-south surface stressu vertical diffusion heating ratev vertical diffusion heating rateT vertical diffusionq vertical diffusion

Units

m 2 . s-2

PaK

m * s-1m-sm~s

Kg Kg- 1

K . s-1K * s-1K . s- 1

Kg. Kg- 1. s- 1

flag

Kmm

m * s-

m * s-1

m * -1

m .* sm - -1

m~s

W * m- 2W * m- 2

W . m - 2

Ks-1K.s-1K.s-1

Kg. KIg-l s- 1

47

Field

PHISPSTUVQNDUHNDVHNDTHNDQHORO

TSWETSNOWHPRECLPRECCPRECSLPRECSCRUNOFFHFLRQFLRNDUSNDVSNDUVNDVVNDTVNDQV

CCM1 Model Variables (cont'd)

Field

FRSAFRLAFIRTPSABTPALBTCLOUDCLOUDECLRLTCLRSTCLRLSCLRSSOMEGAQCTAUXTAUYSRADQRSQRLSOLINUTENDVTENDTTENDQTENDLPSTENDTCONDDQCOND

Description

average net downward solar flux at sfcaverage net upward longwave flux at sfcaverage net longwave flux at top of modelaverage absorbed solar fluxaverage planetary albedo at top of modelfractional cloud covercloud emissivityclear sky upward longwave flux at topclear sky downward solar flux at topclear sky upward longwave flux at surfaceclear sky downward solar flux at surfaceomega vertical velocitytotal condensation rateeast-west surface stressnorth-south surface stresssurface radiative heatingsolar heating ratelongwave heating ratesolar insolationu tendencyv tendencyT tendencyq tendencysurface pressure tendencychange in T from convective adjustmentschange in q from convective adjustments

Units

Wfc m - 2

W . m- 2

W-m- 2W * m- 2

W m- 2

fractionfractionfractionW- m- 2

W7 mf - 2

W- m- 2W e m- 2

W. m- 2

Pa. s- 1

kg * m- 2 s-N K m -2

N * m - 2

W. m- 2

K . s- 1

K s- 1

W m- 2

m° s-2

m e S~ 2m. s

K · s- 1

Kg.Kg- 1. s-Pa. s-K.s-1

Kg . Kg- 1 . s -1

48

_ _ __ ______ __

I .. . .. . - - - -

3.4 User-defined derived fields

The ability to create user-defined derived fields is shown in Example 11. User-definedkeywords are specified using a series of operators in Reverse Polish Notation.

DERFLD = 'Tcels', 111,2,31,0, 'T',273.15, :MINUS', .END'

is an example converting temperature from degrees Kelvin to degrees Celsius. The firstparameter is the name of the derived field ('Tcels'), the second parameter indicates whenthe computation should be done in the code (111 - on input from a hybrid coordinate

tape), the third parameter is the vertical placement flag (2 - multilevel fields located atlayer midpoints), the fourth is the vertical coordinate flag (31 - can compute if data is onany surface), the fifth is the spectral parity flag (0 - parity not applicable), the 273.15 is ascalar value to be applied to the field 'T', and the ':MINUS' is the operator to be applied.Each group defining a derived field ends with the . END' parameter. The result of theabove expression is to subtract 273.15 from all values of the 'T' field. This provides youwith a capability to define fields in terms of other fields without modifying the Processorcode. The operators available apply either to a single value (Unary Functions) or to twovalues (Binary Functions).

49

Unary Functions

Function Description

.ABS absolute value

.ALOG natural logarithm

.ALOG10 common (base 10) logarithm

.CONST create a constant-value multilevel field

.DSTIMES delta sigma times each level

.DSWVSUM delta sigma weighted vertical sum of all levels

.END expression and definition group terminator

.EXP e ** operand

.LEVELnn extract single level nn (counting from bottom)

.MINUS negate operand

.RANDOM create a pseudo-random, multilevel field

.SHIFTDN shift field downward by one level

.SHIFTUP shift field upward by one level

.SQRT square root

.TCOSL multiply operand by cosine of latitude.TSINL multiply operand by sine of latitude.VSUM vertical sum of all levels.ZAV replace operand by zonal average.ZAVDEV replace operand by deviations from zonal average

A complete description of this capability is given in the complete Users' Guide. Please

refer to this document for more detailed information about this capability, including other

examples of the use of the 'DERFLD' keyword.

50

Binary Functions

OP1 is the leftmost operand, OP2 the rightmost.At least one operand must be a field,

unless otherwise noted.

Function Description

:PLUS OP1 + OP2:MINUS OP1 - OP2:TIMES OP1 * OP2:DIVIDE OP1 / OP2:MIN minimum(OP1,OP2):MAX maximum(OPl,OP2):POWER OP1 ** OP2:AMOD mod(OP1,OP2):INVINTB 3-D incremental vertical integral:INVINTT 3-D incremental vertical integral:L1TIMES OPl*(bottom level of OP2) (two fields only)

:EQ .T. iff OP1.EQ.OP2 (iff = if and only if):NE .T. iff OP1.NE.OP2:LT .T. iff OP1.LT.OP2:GT .T. iff OP1.GT.OP2:LE .T. iff OP1.LE.OP2:GE .T. iff OP1.GE.OP2:AND .T. iff OP1.AND.OP2 (two fields only):OR .T. iff OP1.OR.OP2 (two fields only)

:LEVMASK mask field to 0. at certain levels:UNBLOCK field OP1 blocked points take values of corresponding points

at OP2

4.0 Processor Usage

4.1 CCM2 Considerations

Users familiar with processing CCM1 history datasets will find some differences whenprocessing CCM2 datasets. First, a number of the fields output to CCM2 history tapesare different from the CCM1 fields. A list of CCM2 and CCM1 field names, as well as alist of their accompanying Processor derived fields is listed in section 3.3. Second, CCM2utilizes a hybrid sigma-pressure vertical coordinate system rather than the pure sigmavertical coordinate system used by CCM1. Finally, CCM2 history tapes have a slightlydifferent header and data format from CCM1. This is documented in the Users' Guide tothe NCAR CCM2 (Bath et al. 1992). Some general rules for processing CCM2 tapes are:

TYPEc: The Processor automatically recognizes that an input history tape is eitherCCM2, CCM1 or CCMOB format. There is no need to specify this ICP whenreading in a CCM2, CCM1 or CCMOB datasets.

FIELDS: The Processor derived field for geopotential height for CCM2 is Z2.

DERFLD: When using the DERFLD ICP to construct a user defined derived field, use acomputation type of 111 for calculations to be carried out on input from CCM2hybrid coordinate tapes. The standard computation type for calculations to becarried out on input from CCM1 sigma coordinate tapes is 11.

DERFLD: The analogs to the CCM1 user defined derived field .DSWVSUM are :INVINTB andINVINTT.

OFTHST: By default, the format for output history tapes is the same as the format of theinput history tape. OFTHST may be used to manually control the format of theoutput dataset.

4.2 Processor File Management

Both the CCM2 and the Processor have adopted the convention of keeping the tem-

porary disk copies of data files being input and output to Mass Store (MSS) files under theshavano directory: /usr/tmp/ccm. Any MSS files input and output by the Processorwill be written to disk with the name: /usr/tmp/ccm/MSSFILEPATH/MSSFILENAME, where/MSSFILEPATH/MSSFILENAME is the mass store path name of the volume being acquire ordisposed. To keep the file from being scrubbed off the disks during the course of a run,the Processor establishes a link between a file in the local directory (usually $TMPDIR)and the copy of the MSS file under the /usr/tmp/ccm subdirectory.

51

For instance, if the user requests the Mass Store file /CSM/ccm2/414/hist/h0002, the

Processor first checks the Cray disk for the existence of the file

/usr/tmp/ccm/CSM/ccm2/4l4/hist/h0002.

If it exists, the Processor will link it to a local filename. If it doesn't exist, the Processor

will first make the shavano subdirectory /usr/tmp/ccm/CSM/ccm2/414/hist/, then the

MSS file /CSM/ccm2/414/hist/h0002 would be read into the local directory via msread.

The local file will- then be linked to the file:

/usr/tmp/ccm/CSM/ccm2/414/hist/h0002.

In either case, the Processor actually reads the data from the the local version of the file.

This method has a couple of advantages. First, only one copy of each MSS file will

ever exist on the Cray disks. Second, the file in /usr/tmp/ccm will remain beyond the

running time of the current job which will cut down on access to the Mass Store. Finally,

if the user is running with $TMPDIR as their local directory, the linked copy of the file in

the local directory won't be subject to the disk scrubber during the course of the run.

There are a couple of potential problems with this approach. First, subdirectories be-

low /usr/tmp/ccm can be created by non-Processor job without global read/write/execute

permissions. In this case, anyone, other than the owner, trying to create subdirectories

or read files into those subdirectories will get a permission denied error which halts the

Processor. When this happens, it is up to the user to contact the owner of the restricted

subdirectory about changing the permissions. This problem can be avoided through use of

the command umask 000. Second, it may be possible to overflow, the disk space allotted

to /usr/tmp/ccm. For this reason, the default for the ICP DELREL has been changed to 2,

meaning disk copies of MSS files will be deleted as soon as possible.

4.3 Error Handling

If an error exit from the Processor occurs, there is usually at least one, if not several,

error messages printed in the output. Internal Processor error messages can be found

in the body of the output below the listing of the ICP's and before the Cray debugger

output. System messages have been known to appear in the output, often appearing above

the ICP listing.

In many instances, simply increasing the job's memory limits in the QSUB specification

remedies error aborts, particularly when the abort involves ishell calls. The general

subject of error exits from the Processor is discussed in in more detail in section 1.3.5 in

the CCM Modular Processors Users' Guide.

52

4.4 Processor Output

There are at least three output files produced by the processor for most jobs. Thefirst is a printed summary of the processing tasks that were carried out and the totalnumber of plot frames produced. This file is always produced. The second is an optionalplot file, which can then be disposed of by whichever of the options is the most convenientfor the user. The third is the optional save tape output file produced from the run.

Following the description of the printed and graphical output is a sample run createdfrom the ICP script shown in section 2.

4.5 Graphical output

There are several options for plot file disposition. The examples in section 3 illus-trate a number of the different way to dispose of the processor plot files. The keywordsDPLTCA, DPLTCT, DPLTFN, DPLTFT, DPLTCP, DPLTRCP, DPLTMP, DPLTIT and DPLTMFcontrol disposition of the plot file to one or more destinations for a single jobstep. Bydefault, DPLTFT='D1', so that the plots from each jobstep are automatically disposed tomicrofiche.

4.6 Printed output

The printed output file will automatically be returned to the host computer fromwhich the job was submitted to the Cray. It will contain a log of the input ICP's andwhat tasks were performed. Information on the output plot and data files will be printedwhen appropriate.

The following illustrates the type of output you should expect to see from a processor

run. The ICPs are echoed to the output file. The list of days processed and the processing

done are all printed. If no errors are encountered, a message indicating normal terminationand the number of plot frames produced is printed at the bottom. The index of the plotframes generated is also printed. The log file should also be checked to ensure the correctdisposition of the plot file. If any error is encountered, examine the output lines just abovethe beginning of the symbolic debug dump for a processor produced error message (in thecase of a fatal error-the processor also detects and flags nonfatal errors). This will oftensave a great amount of time, since many errors are flagged by the processor, and the ABORT

is called internally to prevent wasted processing.

53

Warning: no access to tty; thus no job control in this shell...shavano: UNICOS 6.1.6, IOS 6.1.6.

92.11.11 11:46:12 IDENTIFIER 46319.shavano NAMEPrincipal Project GAU use:Update Project Allocated Used921109 nnnnnnnn nnn.nnnn n.nnnn

PROCESSOR Last updated: Oct 22 10:42Report Processor bugs to:

plot.sh ..11:00

User: [email protected]

netms -q FLNM-/usr/tmp/nqs.+++++OAIj/gmeta01 DF-BI df-BI MRS-1440 mrs-1440 dc-PT1

***********************************************************************************************************.******* ***

**** INPUT CONTROL PARAMETERS: STARTING JOBSTEP 1**** ______--------------------

CC plot.sh read temperature from a history tape and plotCTITLEATAPESADAYSAFIELDA1PRESSLEHPROJHPCINTDPLTMFENDOFDATA

'Plot.sh: 850,500,200mb T from the CCM2 Control Run''/CSM/ccm2/414/hist/h0002'

11.,12.,13.,14.,15.'T'

850.,500., 200.'RECT''T',850.,5., 'T',500.,10., 'T',200.,0.'MP'

DAY 11.0000 READ FROM CASE A HISTORY TAPE: /CSM/ccm2/414/hist/h0002

*** HYBRID COEFFS ***FULL LEVELS (MIDPOINTS)

LYR A + B A (PO) B (PS)

0.992530.970450.929280.866410.786510.695170.598250.501280.408960.324850.251240.189190.138710.99043E-010.63947E-010.32559E-010.13073E-010.48093E-02

0.00000E+000.13519E-020.51470E-020.10942E-010.18307E-010.26727E-010.35661E-010.44600E-010.53110E-010.60862E-010.67648E-010.73367E-010.78020E-010.81677E-010.63947E-01

0.32559E-010.13073E-010.48093E-02

0.992530.969090.924130.855470.768200.668440.562590.456680.355850.263990.183590.115820.60693E-010.17366E-010.00000E+000.00000E+000.00000E+000.00000E+00

HALF LEVELS (INTERFACES)A + B A (PO) B (PS)

1.00000.985110.95600

0.90330

0.831020.744380.649210.551290.455800.366920.287600.219480.163080.117980.83143E-010,49183E-010.21554E-010.79292E-020.29170E-02

0.00000OE+00O.OOOOOE+000.26838E-020.75413E-020.14204E-010.22190E-010.30963E-010.39989E-010.48791E-010.56984E-010.64296E-010.70575E-010.75774E-010.79931E-010.83143E-010.49183E-010.21554E-010.79292E-020.29170E-02

1.00000.985110.953310.895760.816820.722190.618250.511300.407010.309940.223300.148900.87309E-010.38054E-01.0OOOOOE+00.0OOOOOE+00

0.OOOOOE+00.00000E+00

0.OOOOOE+00

Fig. 6.a Printout from plot.sh. UNICOS system messages are printed first, followed by a shortProcesser "message of the day". The list of input ICPs is echoed to the output, followedby information on the current day being processed and the vertical levels of the inputhistory tape.

54

123456789

10

1112131415

16171819

----------------------------------------------------------------------

VARIABLE. LOCATION WITHIN TYPE OF LOWER BOUNDARYLAYER INTERPOLATION TREATMENT

T MIDPOINT LOG NO SURF,NO EXTRP

VERTICAL INTERPOLATION COMPLETED FOR CASE A








VERTICAL INTERPOLATION COMPLETED FOR CASE A1

INDEX OF PLOTS FOR DISPOSE GROUP 1

FRAME PLOT DESCRIPTION FIELD LEVEL CASE DAY(S)

1.1 Hor. Proj. Contours 180.0W<lon<180.0E,90.S<lat<9 T 850.OP A 11.01.2 Hor. Proj. Contours 180.OW<lon<180.0E,90.0S<lat<90.ON T 500.OP A 11.01.3 Hor. Proj. Contours 180.0W<lon<180.0E,90.0S<lat<90.0N T 200.OP A 11.01.4 Hor. Proj. Contours 180.0W<lon<180.0E,90.0S<lat<90.0 N T 850.0P A 12.01.5 Hor. Proj. Contours 180.0W<lon<180.0E,90.0S<lat<90.ON T 500.OP A 12.01.6 Hor. Proj. Contours 180.0W<lon<180.0E,90.0S<lat<90.0N T 200.OP A 12.01.7 Hor. Proj. Contours 180.OW<lon<180.0E,90.OS<lat<90.0N T 850.OP A 13.01.8 Hor. Proj. Contours 180.OW<lon<180.0E,90.0S<lat<90.0N T 500.0P A 13.01.9 Hor. Proj. Contours 180.0W<lon<180.0E,90.0S<lat<90.ON T 200.0P A 13.01.10 Hor. Proj. Contours 180.0W<lon<180.0E,90.0S<lat<90.0N T 850.OP A 14.01.11 Hor. Proj. Contours 180.0W<lon<180.0E,90.0S<lat<90.0 N T 500.OP A 14.01.12 Hor. Proj. Contours 180.0W<lon<180.0E,90.0S<lat<90.0N T 200.OP A 14.01.13 Hor. Proj. Contours 180.0W<lon<180.0E,90.OS<lat<90.0 N T 850.OP A 15.01.14 Hor. Proj. Contours 180.0W<lon<180.0E,90.0S<lat<90.0N T 500.OP A 15.01.15 Hor. Proj. Contours 180.0W<lon<180.0E,90.0S<lat<90.ON T 200.OP A 15.0

15 PLOT FRAME(S) IN GROUP 1 DISPOSED TO MP: plotmp gmetaOl

**** NORMAL TERMINATION FOR JOBSTEP 1 ******* .***

**** 15 PLOT FRAMES PRODUCED 1 PLOT FILES DISPOSED 0 PLOT FRAMES UNDISPOSED *****************************************************************-***************************** ***************************

**** *NORMAL RUN TERMINATION ******** , ** *

**** TOTAL NUMBER OF PLOT FILE DISPOSE GROUPS: 1 ***************************************** ** ** ******************************************************************

Fig. 6.b Printout from plot.sh (cont'd). The interpolation information and the list of daysread are printed. The index of plots produced by this jobstep is printed followed bythe command used to dispose the plots, in this case, to the SCD laser printer via theplotmp command. Finally, a summary of this jobstep and a run termination summaryare printed.

55

STOP (called by CRAYPR )CP: 19.040s, Wallclock: 61.053s, 3.9% of 8-CPU Machine

HWM mem: 1029321, HWM stack: 6400, Stack overflows: 0

STOP (called by JACC )CP: 0.005s, Wallclock: 4.587sHWM mem: 104835, HWM stack: 3584, Stack overflows: 2

Job Accounting - Summary Report... ,=.sIIIIssI ssIIsIIII ,.PI ..

Job Accounting File NameOperating SystemUser Name (ID)Group Name (ID)Account Name (ID)

Gaus AllocatedGaus Used, as of 11/09/92

Job Name (ID)Report StartsReport EndsElapsed TimeUser CPU TimeSystem CPU TimeI/O Wait Time (Locked)I/O Wait Time (Unlocked)CPU Time Memory IntegralSDS Time Memory IntegralI/O Wait Time Memory IntegralData TransferredMaximum memory usedMaximum SDS usedLogical I/O RequestsPhysical I/O RequestsNumber of Commands

CPU HoursAvg Memory (mwd)Disk Activity (mwd)

0.006150.8428711.90578

Charge before Queue Factor(Excluding MSS/NTWK/TAGS)

Multiplier for econ QueueCharged against Allocation11:47:36 + exitlogout

/usr/tmp/nqs.+++++OAIj/.jacct54327sn1036 sn1036 6.1 cbh.31 CRAY Y-MPccmproc2 (nnnn)ncar (nnn)nnnnnnnn (nnnn)

nnn.nnnnn.nnnn

plot.sh...11:00 (54327)11/11/92 11:46:1611/11/92 11:47:24

68 Seconds19.6564 Seconds2.4864 Seconds18.4476 Seconds7.4470 Seconds18.6635 Mword-seconds0.0000 Mword-seconds14.6596 Mword-seconds11.9058 MWords0.9883 MWords0.0000 MWords

885130745

GAU ComponentsJob ChargeCPU ChargeMemory Charge :Disk Act Charge :

0.50

0.001000.006150.000020.00199

0.00916 GAUs

0.00458 GAUs

Fig. 6.c Printout from plot.sh (cont'd). Following the Processor output, the Job Accounting

information is printed. A couple of key numbers to watch are the User and System CPU

Time, Maximum memory used, as well as the computer resource statistics (GAUs) .

56

INDEX OF PLOTS FOR DISPOSE GROUP 1

_____________________________________ ____________________________________-----_--_ ------___________ ____________"

FRAME PLOT DESCRIPTION FIELD LEVEL CASE OAY(S)

-___________________ ________ ________ ________ _____ _ _ _-- __------_ ---__ ---_ - -------- ---------------------------------_______ ___

Hor. Proj. Contours 180.OW<lon<180.OE.9.Slt90.OS 90.ON

Hor. Proj. Contours 180.OW<lon<180.OE.90.0S<lat<90.ONHor. Proj. Contours 180.OW<Ion<180.OE.90.0S<lat<90. 0ON

Hor. Proj. Contours 180.0W<lon<180.OE.90.OS<lat<90.0NHor. Proj. Contours 180.OW lon<180.OE.90.OS<I at90.ON

Hor. ProJ. Contours 180.OW<lon<180.OE.90.OS<1lt<90.ONHor. Proj. Contours 180.OW<lon<180.0E.90.OS<lt<90.ONHor. Proj. Contours 180.OW<lon<180.OE.90.OS<Iat<90.ONHor. Proj. Contours 180.OW<lon<180.OE.90.OS(<lt<90.ONHor. Proj. Contours 180.OWIlon<180.OE.90.OS<Iat<90.ONHor. Proj. Contours 180.OWIlon<180.OE,90.S<lat<90.ONHor. Proj. Contours 180.OW<Ion<180.OE.90.OS<lat<90.0NHor. Proj. Contours 180.0W<lon<180.OE.90.OS<lat<90.ONHor. Proj. Contours 180.OW<lon<180.OE.90.OS<lat<90.ONHor. Proj. Contours 180.OW<lon<180.OE.90.OS<lat<90.0N

T

TTT

TT

TTTTT

TTTT

oUJu .uvr500 .OP200.OP850. OP500 .OP200.OP850.OP500. OP200.OP850. OP500 .OP200 .OP850.OP500 .OP200. OP

A

AAAAAAAAAAAAAA

11 .

11.011.012.012.012.013.013.013.014.014.014.015.015.015.0

Fig. 7. Index of plots from the first example script, plot. sh.

CASE: 414Plot.sh: 850,500,200mb T

DAY 11.000180o 150W 120oW 90 60W 30W

CASE 414 plx19from the CCM2 Control Run

T 850. OP0 30E 60E 9OE 120E 150E 180E

Contour from 225 to 300 by 5

Fig. 8. Horizontal plot of temperature at 850 mb on day 11.0. This is the first plot generatedfrom the first example script, plot.sh. The first title line shows the model runs casename and title. The second line echos out the TITLEA ICP. The third line displaysthe model day, field-and level for this plot (here the 'P' signifies that the level is on apressure surface). Note the missing contours where the data is blocked over the regionsof high elevation, such as the Tibetan Plateau. The units of the field can be found onthe history tape header.

57

1.11.21.31.41.51.6

1.71.81.91.101.111.121.131.141.15

T - r. no Al 11 1r

5 Summary

The modular processor is an extensive post-processing tool for CCM output data. Theprocessor can be controlled by a series of input control parameters (ICPs) which can beconstructed to generate printed and plotted output and/or other datasets. The informationgiven here serves as an introduction to the use of this post processor.

Hopefully, this tutorial has answered basic questions related to the use of the CCMmodular processor. Any further question related to the processor can be sent via e-mail [email protected].

58

References

Bath, L.M., J. Rosinski, J. Olson, 1992: Users' Guide to NCAR CCM2, NCAR TechnicalReport, NCAR/TN-379+IA.

Bath, L.M., M.A. Dias, D.L. Williamson, G.S. Williamson and R.J. Wolski, 1987: Users' Guideto NCAR CCM1, NCAR Technical Report, NCAR/TN-286+IA.

Williamson, D.L., J.T. Kiehl, V. Ramanathen, R.E. Dickinson and J.J. Hack, 1987: Descriptionof NCAR Community Climate Model (CCM1), NCAR Technical Report, NCAR/TN-285+STR, 112 pp.

Wolski, R., 1987: CCM Modular Processor Users' Guide (Version PROC02). NCAR TechnicalReport, NCAR/TN-290+STR.

59

Glossary

Blocked Point: A gridpoint at which the value of some field is undefined. For example, whenpressure interpolation is request at the 850 mb level, some gridpoints lie below the earth'sphysical surface, so they are blocked.

Case: A set of input data grouped in order to allow comparing it to another Case. The firstcase input is termed Case A; the second is termed Case B. Comparing or merging Cases A andB result in a Case C.

CCM: The NCAR Community Climate Model.

CGD: Climate and Global Dynamics Division, the NCAR division which is responsible for thedevelopment of the Processor and the CCM.

Comparison: Differences or Ratios computed between the fields within Case A and Case B.

Day: A particular Model time at which instantaneous values of fields (see definition below) aredefined.

Derived Field: A derived field is a "new" field which is computed from other specific fieldsat some particular stage of processing. For example, U2+V- 2 can be computed from thecomponent wind fields U and V.

Ensemble: A collection of time series which are to be processed together as a singleProcessor comparison Case (see definition of Case above). For example, a series of perturbationexperiments, all started from the same date, constitute an ensemble.

Field: A set of values of some particular quantity associated with the Model, defined on someset of points in time and (three-dimensional) space. For example, temperature T and zonal windU are fields. The name of each field is designated by a unique string of 1 to 8 characters.

Field pass: One pass through all input data and the associated processing. The numberof fields which can be processed in one pass is limited by the amount of computer memoryavailable.

FTP: The user interface to the standard File Transfer Protocol (FTP). ftp transfers files to andfrom a remote network site.

GAU: General Accounting Unit. A GAU is the NCAR SCD charging unit for computerresources.

GWD: Gravity Wave Drag

History Tape: A volume of data, usually output by the Model or the Processor, consisting ofa sequence of logical records containing the values of Model variables for a series of Model days.

Horizontal Slice Save Tape: A volume of data, output by the Processor, consisting of asequence horizontal data slices. The data consists of each level of a field as horizontal, global,two dimensional arrays.

Hybrid Levels: The default vertical coordinate for CCM2. It is a mix of sigma and pressurelevel systems.

Initial Dataset: A history tape which contains the fields necessary to initialize the prognosticvariables for a model integration.

60

IRJE: Internet Remote Job Entry. The protocol for remote users to easily submit batch jobsto the NCAR Cray computer.

Input Control Parameter (ICP): A parameter which may be set by the user in order tocontrol processing operations.

Jobstep: A single execution of the Processor code. A Processor job consists of one or morejobsteps.

Latitude: Latitude is defined as increasing northward, positive in the northern hemisphere,negative in the southern. Values are always specified in degrees, ranging from -90. to +90.

Level: A point in the Model vertical dimension which has a single value of the verticalcoordinate associated with it. The vertical coordinates may be on either sigma, pressure orhybrid sigma-pressure surfaces.

Longitude: Longitude is defined as increasing eastward, positive east of Greenwich, negativewest of Greenwich. Values are usually in degrees between -180.0 and the last grid point before(west of) +180.0. The dateline is usually designated as -180.0.

LSD: List Sorted Data. A volume of data, output by the Processor, which allows the processeddata to be reordered (sorted) with respect to ensemble member, time, and field/level as it isoutput.

Model: The NCAR Community Climate Model (CCM); more specifically, the version of theCCM being processed.

Masking: The fields being processed may be "masked" by surface type. Any combination ofthe three surface types (land, ocean, sea ice) may be specified. When masking is requested, alllevels of all fields are masked by setting the field values at masked points to the "blocked point"value 1.E36; these points are then excluded from subsequent computations and plotting.

Merge: Combining variables from Case A and Case B to form a new Case C. See documentationon the ICP ABMERGE.

msread: NCAR UNICOS command to copy a data file from the MSS to the Cray disks..

MSS: The NCAR Mass Storage System; this system handles all of the users' longterm storageneeds for large datasets.

Packing: A method for reducing the volume of data produced on history tapes. A packingdensity of 1 means that the data is not packed. A packing density of 4 means that the data hasbeen packed at a 4:1 compression ratio;

Plot Index: A listing of the plots produced by a Processor jobstep.

Processor job: The execution of an entire batch submittal (Cray job script). This may includemore than one "jobstep" because it is possible to reexecute the Processor code in the same Crayjob. This is referred to as "jobstepping".

Save Tape: A data file output by the Processor and saved so that additional processing can bedone at a later time. Save Tapes are usually MSS files, but may also exist (temporarily) onlyon the Cray disks.

SCD: Scientific Computing Division. The NCAR division responsible for maintaining andadministrating the NCAR computing environment.

61

Script: A collection of UNICOS commands collected together as a file which can be executedeither interactively or via the batch queues.

shavano: The node name for the NCAR Cray-YMP 864.

T42: The default spectral truncation for CCM2

TMPDIR: A temporary directory associated with every session on the Cray which is initiallyempty and is removed at the end of the session.

UNICOS: The Cray version of the UNIX operating system.

62

Introduction to the UNICOS CCM processor.

Documents

Transcript of Introduction to the UNICOS CCM processor.