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 (required for history tapes) specifies
which model times are to be processed and can either be requested
explicitly (e.g., 11.0, 12.0, 13.0, 14.0, 15.0), or in shorter, do-loop
notation (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
dependent ICP .  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 .

ther ICPs, such as FIELDA1, also have a numeric suffix.  The numeric
ending indicates 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 dependent ICP .
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.