Clouds and the Earth\'s Radiant Energy System

(CERES)

Data Management System

CERES Time Interpolation and Spatial Averaging (TISA)

(Subsystems 7.1, 8.0, & 10.0)

Test Plan

Release 4

Version 8

**Primary Authors**

*Cathy Nguyen, Raja Raju*

Science Systems and Applications, Inc. (SSAI)

One Enterprise Parkway, Suite 200

Hampton, VA 23666

NASA Langley Research Center

Climate Science Branch

Science Directorate

21 Langley Boulevard

Hampton, VA 23681-2199

SW Delivered to CM: January 2008

Document Date: January 2008

[]{#__RefHeading___Toc188241727 .anchor}Document Revision Record

The Document Revision Record contains information pertaining to approved
document changes. The table lists the date the Software Configuration
Change Request (SCCR) was approved, the Release and Version Number, the
SCCR number, a short description of the revision, and the revised
sections. The document authors are listed on the cover. The Head of the
CERES Data Management Team approves or disapproves the requested changes
based on recommendations of the Configuration Control Board.

+-------+-------+------+-----------------------------------+---------+
| Doc   |       |      |                                   |         |
| ument |       |      |                                   |         |
| Rev   |       |      |                                   |         |
| ision |       |      |                                   |         |
| R     |       |      |                                   |         |
| ecord |       |      |                                   |         |
+=======+=======+======+===================================+=========+
| >     | >     | >    | > Description of Revision         | > Sect  |
| SCCR\ |  Rele | SCCR |                                   | ion(s)\ |
| >     | ase/\ | >    |                                   | > A     |
|  Appr | > Ve  | > Nu |                                   | ffected |
| oval\ | rsion | mber |                                   |         |
| >     | >     |      |                                   |         |
|  Date | > N   |      |                                   |         |
|       | umber |      |                                   |         |
+-------+-------+------+-----------------------------------+---------+
| > 06/ | >     | >    | -   Updated the SCCR number.      | > 2.1   |
| 28/01 |  R3V3 |  276 |                                   | >       |
|       |       |      | -   Updated filenames and         | > 2.2   |
|       |       |      |     compilation commands.         | >       |
|       |       |      |                                   | >       |
|       |       |      | -   Corrected the PGE execution   | 3.1.1.2 |
|       |       |      |     command and updated gif       | >       |
|       |       |      |     filenames.                    | > 3.1.3 |
|       |       |      |                                   | >       |
|       |       |      | -   Added instructions for        | > All   |
|       |       |      |     executing the cleanup script. |         |
|       |       |      |                                   |         |
|       |       |      | -   Updated format to comply with |         |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 04/ | >     | >    | -   Updated the SCCR number.      | > 2.1   |
| 01/02 |  R3V4 |  334 |     Added one tar file.           | >       |
|       |       |      |                                   | > 2.2   |
|       |       |      | -   Updated filenames and         | >       |
|       |       |      |     compilation commands.         | >       |
|       |       |      |                                   | 3.1.1.2 |
|       |       |      | -   Added SRBAVG3 file. Took out  | >       |
|       |       |      |     two .gif files                | >       |
|       |       |      |                                   | 3.1.1.4 |
|       |       |      | -   Changed the total run time,   | >       |
|       |       |      |     memory and required disk      | > All   |
|       |       |      |     space.                        |         |
|       |       |      |                                   |         |
|       |       |      | -   Updated format to comply with |         |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 06/ | >     | >    | -   Updated the SCCR number.      | > 2.1   |
| 17/02 |  R3V5 |  368 |                                   | >       |
|       |       |      | -   Updated to mention the source | >       |
|       |       |      |     environment file.             | 3.1.1.1 |
|       |       |      |                                   | >       |
|       |       |      | -   Changed the total run time,   | >       |
|       |       |      |     memory and required disk      | 3.1.1.4 |
|       |       |      |     space.                        | >       |
|       |       |      |                                   | >       |
|       |       |      | -   Added the locations of the    | 3.1.2.3 |
|       |       |      |     compared data files.          | >       |
|       |       |      |                                   | > All   |
|       |       |      | -   Updated format to comply with |         |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 09/ | >     | >    | -   Updated the SCCR number.      | > 2.1   |
| 03/02 |  R3V6 |  386 |                                   | >       |
|       |       |      | -   Changed the total run time,   | >       |
|       |       |      |     memory and required disk      | 3.1.1.4 |
|       |       |      |     space.                        | >       |
|       |       |      |                                   | > All   |
|       |       |      | -   Updated format to comply with |         |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 01/ | >     | >    | -   Updated the SCCR number.      | > 2.1   |
| 07/03 |  R3V7 |  415 |                                   | >       |
|       |       |      | -   Changed the instrument ID     | >       |
|       |       |      |     from 1 to 3 in the output     | 3.1.1.2 |
|       |       |      |     file names since FM2 is used. | >       |
|       |       |      |                                   | >       |
|       |       |      | -   Changed the total run time,   | 3.1.1.4 |
|       |       |      |     memory and required disk      | >       |
|       |       |      |     space.                        | > All   |
|       |       |      |                                   |         |
|       |       |      | -   Updated format to comply with |         |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 01/ | >     | >    | -   Updated Document Overview to  | > 1.1   |
| 22/03 |  R3V8 |  418 |     add Subsystem 7.1.            | >       |
|       |       |      |                                   | > 1.2   |
|       |       |      | -   Updated Subsystem Overview to | >       |
|       |       |      |     add Subsystem 7.1.            | > 2.0   |
|       |       |      |                                   | >       |
|       |       |      | -   Added Subsystem 7.1.          | > 2.1   |
|       |       |      |                                   | >       |
|       |       |      | -   Updated the SCCR number and   | > 2.2   |
|       |       |      |     added Subsystem 7.1.          | >       |
|       |       |      |                                   | > 3.1   |
|       |       |      | -   Added Subsystem 7.1 and       | >       |
|       |       |      |     updated Subsystem 10.         | >       |
|       |       |      |                                   | 3.1.1.2 |
|       |       |      | -   Added Subsystem 7.1 Main      | >       |
|       |       |      |     Processor.                    | >       |
|       |       |      |                                   | 3.2.1.4 |
|       |       |      | -   Changed the instrument ID     | >       |
|       |       |      |     from 1 to 3 in the output     | > All   |
|       |       |      |     file names since FM2 is used. |         |
|       |       |      |                                   |         |
|       |       |      | -   Changed the total run time,   |         |
|       |       |      |     memory and required disk      |         |
|       |       |      |     space.                        |         |
|       |       |      |                                   |         |
|       |       |      | -   Updated format to comply with |         |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 04/ | >     | >    | -   Updated to change the SCCR    | > 2.1   |
| 08/03 |  R3V9 |  433 |     numbers to XXX.               | >       |
|       |       |      |                                   | >       |
|       |       |      | -   Updated to change the month.  | 3.1.1.1 |
|       |       |      |                                   | >       |
|       |       |      | -   Changed the file range to the | >       |
|       |       |      |     test case.                    | 3.1.1.2 |
|       |       |      |                                   | >       |
|       |       |      | -   Changed the main processor    | >       |
|       |       |      |     summary.                      | 3.1.1.4 |
|       |       |      |                                   | >       |
|       |       |      | -   Updated format to comply with | > All   |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 05/ | >     | >    | -   Updated to change the month.  | >       |
| 29/03 | R3V10 |  440 |                                   | 3.1.1.1 |
|       |       |      | -   Changed the year and month to | >       |
|       |       |      |     variables.                    | >       |
|       |       |      |                                   | 3.1.1.2 |
|       |       |      | -   Changed the main processor    | >       |
|       |       |      |     summary.                      | >       |
|       |       |      |                                   | 3.1.1.4 |
|       |       |      | -   Updated format to comply with | >       |
|       |       |      |     standards.                    | > All   |
+-------+-------+------+-----------------------------------+---------+
| > 08/ | >     | >    | -   Updated to add subsystem      | > 1.2.2 |
| 25/03 | R3V11 |  462 |     overview for Subsystem 8.     | > &     |
|       |       |      |                                   | > 1.2.3 |
|       |       |      | -   Added in the installation for | >       |
|       |       |      |     Subsystem 8.                  | > 2.1   |
|       |       |      |                                   | >       |
|       |       |      | -   Updated to add Subsystem 8 in | > 2.2   |
|       |       |      |     the compilation.              | >       |
|       |       |      |                                   | > 3.2   |
|       |       |      | -   Added the main processor for  | >       |
|       |       |      |     Subsystem 8.                  | > 2.2   |
|       |       |      |                                   | >       |
|       |       |      | -   Changed the compilation       | >       |
|       |       |      |     command for Subsystems 7.1, 8 | 3.1.2.3 |
|       |       |      |     and 10.                       | >       |
|       |       |      |                                   | > All   |
|       |       |      | -   Corrected the number of files |         |
|       |       |      |     delivered in out_exp and      |         |
|       |       |      |     changed the "diff" command to |         |
|       |       |      |     "cmp" command.                |         |
|       |       |      |                                   |         |
|       |       |      | -   Updated format to comply with |         |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 05/ | >     | >    | -   Added the removal of the      | > 2.1   |
| 21/04 | R3V12 |  527 |     ancillary directory.          | >       |
|       |       |      |                                   | >       |
|       |       |      | -   Updated to change the month.  | 3.1.1.1 |
|       |       |      |                                   | >       |
|       |       |      | -   Changed the year and month to | >       |
|       |       |      |     variables.                    | 3.1.1.2 |
|       |       |      |                                   | >       |
|       |       |      | -   Changed the main processor    | >       |
|       |       |      |     summary.                      | 3.1.1.4 |
|       |       |      |                                   | >       |
|       |       |      | -   Updated format to comply with | > All   |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 08/ | >     | >    | -   Changed the name of the tar   | > 2.1   |
| 20/04 | R3V13 |  554 |     file.                         | >       |
|       |       |      |                                   | >       |
|       |       |      | -   Updated to change the month   | 3.2.1.1 |
|       |       |      |     and the file name.            | >       |
|       |       |      |                                   | >       |
|       |       |      | -   Changed run time and memory.  | 3.2.1.4 |
|       |       |      |                                   | >       |
|       |       |      | -   Changed the month for         | >       |
|       |       |      |     Subsystem 10.                 | 3.3.1.1 |
|       |       |      |                                   | >       |
|       |       |      | -   Updated format to comply with | > All   |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 09/ | >     | >    | -   Added more commands to remove | > 2.1   |
| 15/04 |  R4V1 |  516 |     the old directories. Deleted  | >       |
|       |       |      |     one file.                     | > 2.2   |
|       |       |      |                                   | >       |
|       |       |      | -   Changed the directory name.   | >       |
|       |       |      |                                   | 3.3.1.1 |
|       |       |      | -   Updated to change the month   | >       |
|       |       |      |     and the file name.            | >       |
|       |       |      |                                   | 3.3.1.4 |
|       |       |      | -   Changed run time and memory.  | >       |
|       |       |      |                                   | >       |
|       |       |      | -   Changed the script name.      | 3.3.2.3 |
|       |       |      |                                   | >       |
|       |       |      | -   Added Test Procedures for     | > 3.3.4 |
|       |       |      |     Aqua.                         | >       |
|       |       |      |                                   | > All   |
|       |       |      | -   Updated format to comply with |         |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 04/ | >     | >    | -   Added phase one of SRBAVG     | > 1.2.4 |
| 20/05 |  R4V2 |  583 |     run.                          | >       |
|       |       |      |                                   | > 2.1   |
|       |       |      | -   Changed file name. Added to   | >       |
|       |       |      |     remover directories.          | > 2.2   |
|       |       |      |                                   | >       |
|       |       |      | -   Updated to change the file    | >       |
|       |       |      |     name and added one more       | 3.3.1.1 |
|       |       |      |     compilation process for phase | >       |
|       |       |      |     one.                          | >       |
|       |       |      |                                   | 3.3.1.2 |
|       |       |      | -   Changed year, month, file     | >       |
|       |       |      |     name, and changed the script  | >       |
|       |       |      |     name.                         | 3.3.2.3 |
|       |       |      |                                   | >       |
|       |       |      | -   Added one output file.        | >       |
|       |       |      |                                   | 3.3.1.4 |
|       |       |      | -   Added one more file to        | >       |
|       |       |      |     compare.                      | > 3.3.4 |
|       |       |      |                                   | >       |
|       |       |      | -   Changed the total run time.   | >       |
|       |       |      |                                   | 3.3.7.2 |
|       |       |      | -   Added test case for Terra     | >       |
|       |       |      |     FM2.                          | >       |
|       |       |      |                                   |  3.3.10 |
|       |       |      | -   Added comparison for the      | >       |
|       |       |      |     output file for Aqua.         | > 3.4   |
|       |       |      |                                   | >       |
|       |       |      | -   Added test case for Aqua FM4. | > All   |
|       |       |      |                                   |         |
|       |       |      | -   Added a new processor.        |         |
|       |       |      |                                   |         |
|       |       |      | -   Updated format to comply with |         |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 04/ | >     | >    | -   Updated to add descriptions   | > 1.2   |
| 24/06 |  R4V3 |  624 |     of the daily means and the    | >       |
|       |       |      |     cloud in ISCCP format.        | > 2.1   |
|       |       |      |                                   | >       |
|       |       |      | -   Added more files.             | > 2.2   |
|       |       |      |                                   | >       |
|       |       |      | -   Added the PGE name for        | > 3.5   |
|       |       |      |     verification.                 | >       |
|       |       |      |                                   | > All   |
|       |       |      | -   Added the new PGE CER10.1P3.  |         |
|       |       |      |                                   |         |
|       |       |      | -   Updated format to comply with |         |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 06/ | >     | >    | -   Updated to delete the new     | > 2.1   |
| 21/06 |  R4V4 |  629 |     installation part.            | >       |
|       |       |      |                                   | > 3.3,  |
|       |       |      | -   Updated the clean-up scripts  | > 3.4,  |
|       |       |      |     for Subsystem 10.             | > & 3.5 |
|       |       |      |                                   | >       |
|       |       |      | -   Updated format to comply with | > All   |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 07/ | >     | >    | -   Updated to delete the new     | > 2.1   |
| 10/06 |  R4V5 |  631 |     installation part.            | >       |
|       |       |      |                                   | > 3.1   |
|       |       |      | -   Updated to add tests for Aqua | >       |
|       |       |      |     and Terra.                    | > All   |
|       |       |      |                                   |         |
|       |       |      | -   Updated format to comply with |         |
|       |       |      |     standards.                    |         |
+-------+-------+------+-----------------------------------+---------+
| > 10/ | >     | >    | -   Added more tar files.         | > 2.1   |
| 04/06 |  R4V6 |  637 |                                   | >       |
|       |       |      | -   Added compilation for PGE     | > 2.2   |
|       |       |      |     CER10.1P4.                    | >       |
|       |       |      |                                   | > 3.3.7 |
|       |       |      | -   Removed Aqua FM3 and FM4 Test | > &     |
|       |       |      |     Procedure for CER10.1P1.      | > 3.3.8 |
|       |       |      |                                   | >       |
|       |       |      | -   Removed Aqua FM3 and FM4 Test | > 3.4.7 |
|       |       |      |     Procedure for CER10.1P2.      | > &     |
|       |       |      |                                   | >       |
|       |       |      | -   Added CER10.1P4 Main          | > 3.4.8 |
|       |       |      |     Processor.                    | >       |
|       |       |      |                                   | > 3.6   |
|       |       |      | -   Added CER10.1P5 Phase One     | >       |
|       |       |      |     Processor.                    | > 3.7   |
+-------+-------+------+-----------------------------------+---------+
| > 11/ | >     | >    | -   Updated to delete the new     | > 2.1   |
| 15/06 |  R4V7 |  639 |     installation part. Added      | >       |
|       |       |      |     installation part for the new | > 3.2   |
|       |       |      |     PGE.                          | >       |
|       |       |      |                                   | > 3.3   |
|       |       |      | -   Updated stand alone test for  | >       |
|       |       |      |     Terra FM1 and Terra FM2.      | > App.  |
|       |       |      |                                   | > A     |
|       |       |      | -   Added new PGE CER8.2P1.       |         |
|       |       |      |                                   |         |
|       |       |      | -   Deleted "SAIC" and added      |         |
|       |       |      |     "SSAI" to Acronym List.       |         |
+-------+-------+------+-----------------------------------+---------+
| > 10/ | >     | >    | -   Updated stand alone test for  | >       |
| 11/07 |  R4V8 |  660 |     Terra FM2 and Aqua FM3 and    | 3.1.4.1 |
|       |       |      |     FM4.                          | >       |
|       |       |      |                                   | >       |
|       |       |      | -   Document was converted from   | 3.1.7.1 |
|       |       |      |     FrameMaker to Word.           | >       |
|       |       |      |                                   | > 3     |
|       |       |      |                                   | .1.10.1 |
|       |       |      |                                   | >       |
|       |       |      |                                   | > All   |
+-------+-------+------+-----------------------------------+---------+

[Document Revision Record ii](#__RefHeading___Toc188241727)

[1.0 Introduction 1](#introduction)

[1.1. Document Overview 1](#document-overview)

[1.2. Subsystem Overview 1](#subsystem-overview)

[1.2.1. CERES Time Space Interpolation (TSI) Subsystem 7.1 Main
Processor
1](#ceres-time-space-interpolation-tsi-subsystem-7.1-main-processor)

[1.2.2. Compute Regional, Zonal, and Global Averages Subsystem 8.0\
Main Processor
2](#compute-regional-zonal-and-global-averages-subsystem-8.0-main-processor)

[1.2.3. Compute Monthly and Regional TOA and SRB Averages Subsystem\
10.0 Main Processor
3](#compute-monthly-and-regional-toa-and-srb-averages-subsystem-10.0-main-processor)

[1.2.4. Compute Monthly Hourly CERES Clear-sky Albedo, CERES Clear-sky\
map and Monthly Regional Snow/Ice Map
3](#compute-monthly-hourly-ceres-clear-sky-albedo-ceres-clear-sky-map-and-monthly-regional-snowice-map)

[1.2.5. Compute Daily and Regional TOA and SRB Averages and Produce\
ISCCP Format Cloud Types
4](#compute-daily-and-regional-toa-and-srb-averages-and-produce-isccp-format-cloud-types)

[2.0 Software and Data File Installation Procedures
5](#software-and-data-file-installation-procedures)

[2.1. Installation 5](#installation)

[2.2. Compilation 7](#compilation)

[3.0 Test and Evaluation Procedures 10](#test-and-evaluation-procedures)

[3.1. CER7.1.1P1 Main Processor for Subsystem 7.1
10](#cer7.1.1p1-main-processor-for-subsystem-7.1)

[3.1.1. Stand-alone Test Procedures for Terra FM1
10](#stand-alone-test-procedures-for-terra-fm1)

[3.1.1.1. PCF Generator 10](#pcf-generator)

[3.1.1.2. Execution 11](#execution)

[3.1.1.3. Exit Codes 11](#exit-codes)

[3.1.1.4. Main Processor Test Summary 11](#main-processor-test-summary)

[3.1.2. Evaluation Procedures 12](#evaluation-procedures)

[3.1.2.1. Log and Status File Results 12](#log-and-status-file-results)

[3.1.2.2. Metadata 12](#metadata)

[3.1.2.3. Execution of Comparison Software
12](#execution-of-comparison-software)

[3.1.3. Solutions to Possible Problems
12](#solutions-to-possible-problems)

[3.1.4. Stand-alone Test Procedures for Terra FM2
13](#stand-alone-test-procedures-for-terra-fm2)

[3.1.4.1. PCF Generator 13](#pcf-generator-1)

[3.1.4.2. Execution 14](#execution-1)

[3.1.4.3. Exit Codes 14](#exit-codes-1)

[3.1.4.4. Main Processor Test Summary
14](#main-processor-test-summary-1)

[3.1.5. Evaluation Procedures 14](#evaluation-procedures-1)

[3.1.5.1. Log and Status File Results
14](#log-and-status-file-results-1)

[3.1.5.2. Metadata 15](#metadata-1)

[3.1.5.3. Execution of Comparison Software
15](#execution-of-comparison-software-1)

[3.1.6. Solutions to Possible Problems
15](#solutions-to-possible-problems-1)

[3.1.7. Stand-alone Test Procedures for Aqua FM3
16](#stand-alone-test-procedures-for-aqua-fm3)

[3.1.7.1. PCF Generator 16](#pcf-generator-2)

[3.1.7.2. Execution 16](#execution-2)

[3.1.7.3. Exit Codes 17](#exit-codes-2)

[3.1.7.4. Main Processor Test Summary
17](#main-processor-test-summary-2)

[3.1.8. Evaluation Procedures 17](#evaluation-procedures-2)

[3.1.8.1. Log and Status File Results
17](#log-and-status-file-results-2)

[3.1.8.2. Metadata 17](#metadata-2)

[3.1.8.3. Execution of Comparison Software
18](#execution-of-comparison-software-2)

[3.1.9. Solutions to Possible Problems
18](#solutions-to-possible-problems-2)

[3.1.10. Stand-alone Test Procedures for Aqua FM4
19](#stand-alone-test-procedures-for-aqua-fm4)

[3.1.10.1. PCF Generator 19](#pcf-generator-3)

[3.1.10.2. Execution 19](#execution-3)

[3.1.10.3. Exit Codes 20](#exit-codes-3)

[3.1.10.4. Main Processor Test Summary
20](#main-processor-test-summary-3)

[3.1.11. Evaluation Procedures 20](#evaluation-procedures-3)

[3.1.11.1. Log and Status File Results
20](#log-and-status-file-results-3)

[3.1.11.2. Metadata 20](#metadata-3)

[3.1.11.3. Execution of Comparison Software
21](#execution-of-comparison-software-3)

[3.1.12. Solutions to Possible Problems
21](#solutions-to-possible-problems-3)

[3.2. CER8.1P1 Main Processor 22](#cer8.1p1-main-processor)

[3.2.1. Stand Alone Test Procedures for Terra FM1
22](#stand-alone-test-procedures-for-terra-fm1-1)

[3.2.1.1. PCF Generator 22](#pcf-generator-4)

[3.2.1.2. Execution 22](#execution-4)

[3.2.1.3. Exit Codes 23](#exit-codes-4)

[3.2.1.4. Main Processor Test Summary
23](#main-processor-test-summary-4)

[3.2.2. Evaluation Procedures 23](#evaluation-procedures-4)

[3.2.2.1. Log and Status File Results
23](#log-and-status-file-results-4)

[3.2.2.2. Metadata 23](#metadata-4)

[3.2.2.3. Execution of Comparison Software
23](#execution-of-comparison-software-4)

[3.2.3. Solutions to Possible Problems
24](#solutions-to-possible-problems-4)

[3.2.4. Stand Alone Test Procedures for Terra FM2
24](#stand-alone-test-procedures-for-terra-fm2-1)

[3.2.4.1. PCF Generator 24](#pcf-generator-5)

[3.2.4.2. Execution 25](#execution-5)

[3.2.4.3. Exit Codes 25](#exit-codes-5)

[3.2.4.4. Main Processor Test Summary
25](#main-processor-test-summary-5)

[3.2.5. Evaluation Procedures 25](#evaluation-procedures-5)

[3.2.5.1. Log and Status File Results
25](#log-and-status-file-results-5)

[3.2.5.2. Metadata 25](#metadata-5)

[3.2.5.3. Execution of Comparison Software
26](#execution-of-comparison-software-5)

[3.2.6. Solutions to Possible Problems
26](#solutions-to-possible-problems-5)

[3.3. CER8.2P1 Post Processor 27](#cer8.2p1-post-processor)

[3.3.1. Stand Alone Test Procedures for Terra FM1
27](#stand-alone-test-procedures-for-terra-fm1-2)

[3.3.1.1. PCF Generator 27](#pcf-generator-6)

[3.3.1.2. Execution 28](#execution-6)

[3.3.1.3. Exit Codes 28](#exit-codes-6)

[3.3.1.4. Main Processor Test Summary
29](#main-processor-test-summary-6)

[3.3.2. Evaluation Procedures 29](#evaluation-procedures-6)

[3.3.2.1. Log and Status File Results
29](#log-and-status-file-results-6)

[3.3.2.2. Execution of Comparison Software
29](#execution-of-comparison-software-6)

[3.3.3. Solutions to Possible Problems
29](#solutions-to-possible-problems-6)

[3.3.4. Stand Alone Test Procedures for Terra FM2
29](#stand-alone-test-procedures-for-terra-fm2-2)

[3.3.4.1. PCF Generator 29](#pcf-generator-7)

[3.3.4.2. Execution 30](#execution-7)

[3.3.4.3. Exit Codes 31](#exit-codes-7)

[3.3.4.4. Main Processor Test Summary
31](#main-processor-test-summary-7)

[3.3.5. Evaluation Procedures 31](#evaluation-procedures-7)

[3.3.5.1. Log and Status File Results
32](#log-and-status-file-results-7)

[3.3.5.2. Execution of Comparison Software
32](#execution-of-comparison-software-7)

[3.3.6. Solutions to Possible Problems
32](#solutions-to-possible-problems-7)

[3.4. CER10.1P1 Main Processor 33](#cer10.1p1-main-processor)

[3.4.1. Stand-alone Test Procedures for Terra FM1
33](#stand-alone-test-procedures-for-terra-fm1-3)

[3.4.1.1. PCF Generator 33](#pcf-generator-8)

[3.4.1.2. Execution 34](#execution-8)

[3.4.1.3. Exit Codes 36](#exit-codes-8)

[3.4.1.4. Main Processor Test Summary
36](#main-processor-test-summary-8)

[3.4.2. Evaluation Procedures 36](#evaluation-procedures-8)

[3.4.2.1. Log and Status File Results
36](#log-and-status-file-results-8)

[3.4.2.2. Metadata 36](#metadata-6)

[3.4.2.3. Execution of Comparison Software
36](#execution-of-comparison-software-8)

[3.4.3. Solutions to Possible Problems
37](#solutions-to-possible-problems-8)

[3.4.4. Stand-alone Test Procedures for Terra FM2
38](#stand-alone-test-procedures-for-terra-fm2-3)

[3.4.4.1. PCF Generator 38](#pcf-generator-9)

[3.4.4.2. Execution 39](#execution-9)

[3.4.4.3. Exit Codes 41](#exit-codes-9)

[3.4.4.4. Main Processor Test Summary
41](#main-processor-test-summary-9)

[3.4.5. Evaluation Procedures 41](#evaluation-procedures-9)

[3.4.5.1. Log and Status File Results
41](#log-and-status-file-results-9)

[3.4.5.2. Metadata 41](#metadata-7)

[3.4.5.3. Execution of Comparison Software
41](#execution-of-comparison-software-9)

[3.4.6. Solutions to Possible Problems
42](#solutions-to-possible-problems-9)

[3.5. CER10.1P2 Main Processor 43](#cer10.1p2-main-processor)

[3.5.1. Stand Alone Test Procedures for Terra FM1
43](#stand-alone-test-procedures-for-terra-fm1-4)

[3.5.1.1. PCF Generator 43](#pcf-generator-10)

[3.5.1.2. Execution 44](#execution-10)

[3.5.1.3. Exit Codes 44](#exit-codes-10)

[3.5.1.4. Main Processor Test Summary
44](#main-processor-test-summary-10)

[3.5.2. Evaluation Procedures 44](#evaluation-procedures-10)

[3.5.2.1. Log and Status File Results
44](#log-and-status-file-results-10)

[3.5.2.2. Metadata 44](#metadata-8)

[3.5.2.3. Execution of Comparison Software
44](#execution-of-comparison-software-10)

[3.5.3. Solutions to Possible Problems
45](#solutions-to-possible-problems-10)

[3.5.4. Stand Alone Test Procedures for Terra FM2
46](#stand-alone-test-procedures-for-terra-fm2-4)

[3.5.4.1. PCF Generator 46](#pcf-generator-11)

[3.5.4.2. Execution 46](#execution-11)

[3.5.4.3. Exit Codes 47](#exit-codes-11)

[3.5.4.4. Main Processor Test Summary
47](#main-processor-test-summary-11)

[3.5.5. Evaluation Procedures 47](#evaluation-procedures-11)

[3.5.5.1. Log and Status File Results
47](#log-and-status-file-results-11)

[3.5.5.2. Metadata 47](#metadata-9)

[3.5.5.3. Execution of Comparison Software
47](#execution-of-comparison-software-11)

[3.5.6. Solutions to Possible Problems
48](#solutions-to-possible-problems-11)

[3.6. CER10.1P3 Main Processor 49](#cer10.1p3-main-processor)

[3.6.1. Stand-alone Test Procedures for Terra FM1
49](#stand-alone-test-procedures-for-terra-fm1-5)

[3.6.1.1. PCF Generator and Execution 49](#pcf-generator-and-execution)

[3.6.1.2. Execution 50](#execution-12)

[3.6.1.3. Exit Codes 50](#exit-codes-12)

[3.6.1.4. Main Processor Test Summary
50](#main-processor-test-summary-12)

[3.6.2. Evaluation Procedures 50](#evaluation-procedures-12)

[3.6.2.1. Log and Status File Results
50](#log-and-status-file-results-12)

[3.6.2.2. Metadata 50](#metadata-10)

[3.6.2.3. Execution of Comparison Software
51](#execution-of-comparison-software-12)

[3.6.3. Solutions to Possible Problems
51](#solutions-to-possible-problems-12)

[3.6.4. Stand-alone Test Procedures for Terra FM2
52](#stand-alone-test-procedures-for-terra-fm2-5)

[3.6.4.1. PCF Generator and Execution
52](#pcf-generator-and-execution-1)

[3.6.4.2. Execution 52](#execution-13)

[3.6.4.3. Exit Codes 53](#exit-codes-13)

[3.6.4.4. Main Processor Test Summary
53](#main-processor-test-summary-13)

[3.6.5. Evaluation Procedures 53](#evaluation-procedures-13)

[3.6.5.1. Log and Status File Results
53](#log-and-status-file-results-13)

[3.6.5.2. Metadata 53](#metadata-11)

[3.6.5.3. Execution of Comparison Software
53](#execution-of-comparison-software-13)

[3.6.6. Solutions to Possible Problems
54](#solutions-to-possible-problems-13)

[3.6.7. Stand-alone Test Procedures for Aqua FM3
55](#stand-alone-test-procedures-for-aqua-fm3-1)

[3.6.7.1. PCF Generator and Execution
55](#pcf-generator-and-execution-2)

[3.6.7.2. Execution 55](#execution-14)

[3.6.7.3. Exit Codes 56](#exit-codes-14)

[3.6.7.4. Main Processor Test Summary
56](#main-processor-test-summary-14)

[3.6.8. Evaluation Procedures 56](#evaluation-procedures-14)

[3.6.8.1. Log and Status File Results
56](#log-and-status-file-results-14)

[3.6.8.2. Metadata 56](#metadata-12)

[3.6.8.3. Execution of Comparison Software
56](#execution-of-comparison-software-14)

[3.6.9. Solutions to Possible Problems
57](#solutions-to-possible-problems-14)

[3.6.10. Stand-alone Test Procedures for Aqua FM4
58](#stand-alone-test-procedures-for-aqua-fm4-1)

[3.6.10.1. PCF Generator 58](#pcf-generator-12)

[3.6.10.2. Execution 58](#execution-15)

[3.6.10.3. Exit Codes 59](#exit-codes-15)

[3.6.10.4. Main Processor Test Summary
59](#main-processor-test-summary-15)

[3.6.11. Evaluation Procedures 59](#evaluation-procedures-15)

[3.6.11.1. Log and Status File Results
59](#log-and-status-file-results-15)

[3.6.11.2. Metadata 59](#metadata-13)

[3.6.11.3. Execution of Comparison Software
59](#execution-of-comparison-software-15)

[3.6.12. Solutions to Possible Problems
60](#solutions-to-possible-problems-15)

[3.7. CER10.1P4 Main Processor 61](#cer10.1p4-main-processor)

[3.7.1. Stand-alone Test Procedures for Aqua FM3
61](#stand-alone-test-procedures-for-aqua-fm3-2)

[3.7.1.1. PCF Generator 61](#pcf-generator-13)

[3.7.1.2. Execution 62](#execution-16)

[3.7.1.3. Exit Codes 64](#exit-codes-16)

[3.7.1.4. Main Processor Test Summary
64](#main-processor-test-summary-16)

[3.7.2. Evaluation Procedures 64](#evaluation-procedures-16)

[3.7.2.1. Log and Status File Results
64](#log-and-status-file-results-16)

[3.7.2.2. Metadata 64](#metadata-14)

[3.7.2.3. Execution of Comparison Software
64](#execution-of-comparison-software-16)

[3.7.3. Solutions to Possible Problems
64](#solutions-to-possible-problems-16)

[3.7.4. Stand-alone Test Procedures for Aqua FM4
66](#stand-alone-test-procedures-for-aqua-fm4-2)

[3.7.4.1. PCF Generator 66](#pcf-generator-14)

[3.7.4.2. Execution 67](#execution-17)

[3.7.4.3. Exit Codes 69](#exit-codes-17)

[3.7.4.4. Main Processor Test Summary
69](#main-processor-test-summary-17)

[3.7.5. Evaluation Procedures 69](#evaluation-procedures-17)

[3.7.5.1. Log and Status File Results
69](#log-and-status-file-results-17)

[3.7.5.2. Metadata 69](#metadata-15)

[3.7.5.3. Execution of Comparison Software
69](#execution-of-comparison-software-17)

[3.7.6. Solutions to Possible Problems
69](#solutions-to-possible-problems-17)

[3.8. CER10.1P5 Main Processor 71](#cer10.1p5-main-processor)

[3.8.1. Stand Alone Test Procedures for Aqua FM3
71](#stand-alone-test-procedures-for-aqua-fm3-3)

[3.8.1.1. PCF Generator 71](#pcf-generator-15)

[3.8.1.2. Execution 72](#execution-18)

[3.8.1.3. Exit Codes 72](#exit-codes-18)

[3.8.1.4. Main Processor Test Summary
72](#main-processor-test-summary-18)

[3.8.2. Evaluation Procedures 72](#evaluation-procedures-18)

[3.8.2.1. Log and Status File Results
72](#log-and-status-file-results-18)

[3.8.2.2. Metadata 72](#metadata-16)

[3.8.2.3. Execution of Comparison Software
72](#execution-of-comparison-software-18)

[3.8.3. Solutions to Possible Problems
73](#solutions-to-possible-problems-18)

[3.8.4. Stand Alone Test Procedures for Aqua FM4
74](#stand-alone-test-procedures-for-aqua-fm4-3)

[3.8.4.1. PCF Generator 74](#pcf-generator-16)

[3.8.4.2. Execution 74](#execution-19)

[3.8.4.3. Exit Codes 75](#exit-codes-19)

[3.8.4.4. Main Processor Test Summary
75](#main-processor-test-summary-19)

[3.8.5. Evaluation Procedures 75](#evaluation-procedures-19)

[3.8.5.1. Log and Status File Results
75](#log-and-status-file-results-19)

[3.8.5.2. Metadata 75](#metadata-17)

[3.8.5.3. Execution of Comparison Software
75](#execution-of-comparison-software-19)

[3.8.6. Solutions to Possible Problems
76](#solutions-to-possible-problems-19)

[Appendix A - Acronyms and Abbreviations
A-1](#acronyms-and-abbreviations)

[Appendix B - Directory Structure Diagrams
B-1](#directory-structure-diagrams)

[Appendix C - File Description Tables C-1](#file-description-tables)

[C.1. Production Script C-1](#production-script)

[C.2. Executables C-1](#executables)

[C.3. Status Message Files C-2](#status-message-files)

[C.4. Ancillary Input Data C-2](#ancillary-input-data)

[C.5. Processing Control Files (PCF), Metadata Control Files (MCF)
C-3](#processing-control-files-pcf-metadata-control-files-mcf)

[Figure B‑1. Directory Structure for the TISA Averaging (tisa_avg) Tar
File B-1](#__RefHeading___Toc188239716)

[Table 3‑1. Test Summary for PGE 7.1.1P1
11](#__RefHeading___Toc188179457)

[Table 3‑2. Test Summary for PGE 7.1.1P1
14](#__RefHeading___Toc188179458)

[Table 3‑3. Test Summary for PGE 7.1.1P1
17](#__RefHeading___Toc188179459)

[Table 3‑4. Test Summary for PGE 7.1.1P1
20](#__RefHeading___Toc188179460)

[Table C.1‑1. Production Scripts @ (\$CERESHOME/tisa_avg/bin)
C-1](#__RefHeading___Toc188179477)

[Table C.2‑1. Executables C-1](#__RefHeading___Toc188179478)

[Table C.3‑1. Status Message Files @ (\$CERESHOME/tisa_avg/smf)
C-2](#__RefHeading___Toc188179479)

[Table C.4‑1. Ancillary Input Data @
(\$CERESHOME/tisa_avg/data/ancillary/static)
C-2](#__RefHeading___Toc188179480)

[Table C.5‑1. Process Control Files (PCF) @ (CERESHOME/tisa_avg/rcf)
C-3](#__RefHeading___Toc188179481)

[Table C.5‑2. Metadata Control Files (MCF) for Subsystem 10.0 @
(\$CERESHOME/tisa_avg/rcf) C-3](#__RefHeading___Toc188179482)

# Introduction

The Clouds and the Earth's Radiant Energy System (CERES) is a key
component of the Earth Observing System (EOS) program. The CERES
instrument provides radiometric measurements of the Earth\'s atmosphere
from three broadband channels: a shortwave channel (0.3 - 5 μm), a total
channel (0.3 - 200 μm), and an infrared window channel (8 - 12 μm). The
CERES instruments are improved models of the Earth Radiation Budget
Experiment (ERBE) scanner instruments, which operated from 1984 through
1990 on the National Aeronautics and Space Administration's (NASA) Earth
Radiation Budget Satellite (ERBS) and on the National Oceanic and
Atmospheric Administration's (NOAA) operational weather satellites
NOAA-9 and NOAA-10. The strategy of flying instruments on
Sun-synchronous, polar orbiting satellites, such as NOAA-9 and NOAA-10,
simultaneously with instruments on satellites that have precessing
orbits in lower inclinations, such as ERBS, was successfully developed
in ERBE to reduce time sampling errors. CERES continues that strategy by
flying instruments on the polar orbiting EOS platforms simultaneously
with an instrument on the Tropical Rainfall Measuring Mission (TRMM)
spacecraft, which has an orbital inclination of 35 degrees. In addition,
to reduce the uncertainty in data interpretation and to improve the
consistency between the cloud parameters and the radiation fields, CERES
includes cloud imager data and other atmospheric parameters. The TRMM
satellite carries one CERES instrument while the EOS satellites carry
two CERES instruments, one operating in a fixed azimuth plane scanning
mode (FAPS) for continuous Earth sampling and the other operating in a
rotating azimuth plane scan mode (RAPS) for improved angular sampling.

## Document Overview

This document, the [CERES Release 4 Test Plan for the Time Interpolation
and Averaging Subsystems 7.1 and Subsystem 10.0, Version 1]{.underline},
provides a description of the CERES Time Interpolation and Spatial
Averaging Release 3 software and supporting data files and explains the
procedures for installing, executing, and testing the software. A
section is also included on validating the results of executing the
software. A description of acronyms and abbreviations is provided in
Appendix A, a directory structure diagram is contained in Appendix B,
and a description of the software and data files is contained in
Appendix C.

The document is organized as follows.

Section 1.0 - Introduction

Section 2.0 - Software and Data File Installation Procedures

Section 3.0 - Test and Evaluation Procedures

Appendix A - Acronyms and Abbreviations

Appendix B - Directory Structure Diagrams

Appendix C - File Description Tables

## Subsystem Overview

### CERES Time Space Interpolation (TSI) Subsystem 7.1 Main Processor

The time interpolation process (7.1), one of the two key parts of
Subsystem 7.0, temporally interpolates CERES data and produces global
synoptic maps of top-of-the-atmosphere (TOA) fluxes and cloud properties
on a 1.0-degree equal-area grid. Another key part of Subsystem 7.0, the
Synoptic Surface and Atmospheric Radiation Budget (SARB), Subsystem 7.2,
produces the Intermediate Synoptic Radiative Fluxes and Clouds (SYNI),
which contains the vertical structure of atmospheric and surface flux
using the interpolated data as input and boundary conditions.

The main input to the time interpolation process is the Hourly Gridded
Single Satellite Fluxes and Clouds (FSW) product, produced by
Atmospheric Gridding and Spatial Averaging, Subsystem 6.0. The gridded
shortwave (SW) and longwave (LW) TOA fluxes and cloud information are
the key items to be interpolated. The radiative profile will be
recalculated in the SARB part of Subsystem 7.0 using the interpolated
fluxes as constraints. This process produces the internal product, Time
Space Interpolate (TSI). These files contain nested grid region data
which is the input to Subsystem 7.2.

The time interpolation process produces global maps of TOA total-sky LW
and SW flux, TOA clear-sky LW and SW flux, TOA window radiances, and
cloud properties at Universal Time (UT) for every day of the month. The
process of producing synoptic maps involves:

1.  Cloud properties from the CERES times of observation are
    interpolated for every hour of the month.

2.  The CERES TOA LW and SW fluxes are interpolated for every hour using
    geostationary data to assist in modeling meteorological variations
    between times of observations.

### Compute Regional, Zonal, and Global Averages Subsystem 8.0 Main Processor

The Monthly Regional, Zonal, and Global Radiation Fluxes and Cloud
Properties Subsystem 8.0 produces regional, zonal and global monthly and
monthly-hourly means. These means are calculated from one month of
synoptic maps on a regional basis and then combined to produce zonal and
global averages.

The main input to this Subsystem is the Surface and Atmospheric
Radiation Budget (SARB) product, produced by Subsystem 7.2, SYNI. This
product contains one month of 3-hourly synoptic maps of
top-of-atmosphere (TOA) LW and SW fluxes, TOA window fluxes, upwelling
and downwelling SW and LW fluxes at each standard CERES pressure level,
and numerous cloud parameters for each region of the CERES global
1.0-degree equal-area grid. The flux parameters include both total-sky
and clear-sky.

The three archival products output from this Subsystem are the Monthly
Regional Radiative Fluxes and Clouds (AVG) product (HDF format) which
contains regional monthly and monthly-hourly means of fluxes and cloud
parameters, the Monthly Zonal and Global Radiative Fluxes, Clouds (ZAVG)
product (HDF format) which contains the zonal and global monthly and
cloud parameters, and the Synoptic Radiative Fluxes and Clouds (SYN)
product (HDF format) which contains regional synoptic hourly means of
fluxes and cloud parameters.

The main steps involved in the averaging process are:

1.  Read the synoptically ordered data.

```{=html}
<!-- -->
```
3.  Average the flux data to produce regional synoptic hourly, monthly
    and monthly-hourly means.

4.  Average the cloud properties using the specified weighting schemes
    to produce regional synoptic hourly, monthly and monthly-hourly
    means.

5.  Average the regional means to produce zonal means.

6.  Average the zonal means to produce global means.

### Compute Monthly and Regional TOA and SRB Averages Subsystem 10.0 Main Processor

The Monthly Regional TOA and SRB Averages Subsystem (10.0) computes
averages of TOA longwave (LW) and shortwave (SW) fluxes, surface fluxes,
and cloud properties on regional, zonal, and global spatial scales. The
main input to Subsystem 10.0 is the Hourly Gridded Single Satellite TOA
and Surface Fluxes and Clouds (SFC) product produced by Surface Gridding
and Spatial Averaging Subsystem (9). SFC contains hourly single
satellite flux and cloud properties averaged over 1.0-degree regions.
Subsystem 10.0 produces the Monthly Regional TOA and SRB Averages
(SRBAVG) product (HDF-EOS format). Two methods are used to compute the
regional TOA total-sky flux averages. TOA flux estimates from both of
the two methods are used to produce estimates of surface flux at all
temporal and spatial scales using the TOA-to-surface flux
parameterization schemes for shortwave and longwave.

The process of producing the means stored in SRBAVG involves:

1.  The TOA clear-sky flux data, surface flux data, and the cloud
    property data are linearly interpolated.

```{=html}
<!-- -->
```
7.  Monthly and monthly-hourly means are calculated from the
    interpolated fluxes and cloud properties on regional, zonal, and
    global scales.

### Compute Monthly Hourly CERES Clear-sky Albedo, CERES Clear-sky map and Monthly Regional Snow/Ice Map

The Clear-sky Map, the Monthly Hourly CERES clear-sky Albedo and Monthly
Regional Snow/Ice Map are required for inputs into Subsystem 10.0. The
main input are the Hourly Gridded Single Satellite TOA and Surface
Fluxes and Clouds (SFC) product from Subsystem 9.

The process of producing the Monthly Hourly CERES clear-sky Albedo, the
Clear-sky map and the Monthly Snow/Ice map involved:

1.  The TOA clear-sky flux data and the cloud property data are linearly
    interpolated.

```{=html}
<!-- -->
```
8.  Monthly and monthly-hourly means are calculated from the
    interpolated fluxes and cloud properties on regional.

9.  The CERES clear-sky albedos were computed and the adjusted depending
    on the regional surface type to create the proper clear-sky map.

10. From the surface input data from gridding, the snow and ice data are
    averaged for each region.

### Compute Daily and Regional TOA and SRB Averages and Produce ISCCP Format Cloud Types 

The regional daily averages of TOA fluxes, surface fluxes, aerosol data
and cloud data are stored in additional SRBAVG_Daily1 and SRBAVG_Daily2.
The GGEO cloud data in ISCCP format are stored in SRBAVG-ISCCP-D2-like1,
and the MODIS cloud data in ISCCP format are stored in
SRBAVG-ISCCP-D2-like2. A QC-ISCCP-D2-NITE is also produced for the
nighttime MODIS cloud.

The process of computing daily and regional TOA and SRB averages and
producing ISCCP format cloud types involved:

1.  GGEO TOA fluxes, surface fluxes and the merged GGEO and CERES cloud
    data are averaged daily for each region.

```{=html}
<!-- -->
```
11. CERES TOA fluxes, ocean and land aerosol data, snow/ice from the ten
    minutes snow map, the zonal solar incident and the MODIS cloud data
    are also averaged daily

12. GGEO and MODIS cloud are averaged into 15 ISCCP cloud types and 9
    GMT time slots for each region.

# Software and Data File Installation Procedures

This section describes how to install Time Interpolation and Space
Averaging (TISA) Averaging Subsystems 7.1, 8.0, and 10.0 software in
preparation for making the necessary test runs at the Langley
Atmospheric Sciences Data Center (ASDC). The installation procedures
include instructions for uncompressing and untarring the delivered tar
files, properly defining environmental variables, and compiling the TISA
Averaging source code.

## Installation

Software/Delta File Install Procedure:

1.  The scripts, Makefile, and Process Control Files in Subsystems 7.1
    and Subsystem 10.0 expect the CERES environment variable,
    **\$CERESENV**, to point to a file which sets the following
    environment variables:

**PGSDIR** Directory for **Toolkit** libraries

**F90** Pointer to the SGI F90 64-bit compiler

**CERESHOME** Top Directory for CERES software

**CERESLIB** Directory for CERESlib

**F90COMP, FCOMP** SGI 64-bit Fortran 90 compile flags

**F90LOAD** SGI 64-bit Fortran 90 load flags

**PGSMSG** Directory which contains **Toolkit and CERES**

Status Message Files

**PGSINC** Pointer to the PGS include file directory

**HDFDIR** Pointer to the HDF home directory

**HDFEOSDIR** Pointer to the HDF-EOS home directory

13. Change directory to the directory where you plan to install the TISA
    Averaging Subsystem. The following instructions assume that the
    directory will be **\$CERESHOME**.

14. For **Subsystem 7.1**, uncompress and untar the tar files by
    replacing **XXX** with the appropriate SCCR number and typing the
    following commands:

**source \$CERESENV**

**cd \$CERESHOME/tisa_avg/data/data_7**

**rm -r out_comp**

**rm -r out_exp**

**rm -r input**

**cd \$CERESHOME**

**uncompress TISAavg_anc_R4-XXX.tar.Z**

**tar xvf TISAavg_anc_R4-XXX.tar**

**uncompress TISAavg_src_1_R4-XXX.tar.Z**

**tar xvf TISAavg_src_1_R4-XXX.tar**

**On Warlock:**

**uncompress TISAavg_data7_1_warlock_R4-XXX.tar.Z**

**tar xvf TISAavg_data7_1_warlock_R4-XXX.tar**

**uncompress TISAavg_data7_2_warlock_R4-XXX.tar.Z**

**tar xvf TISAavg_data7_2_warlock_R4-XXX.tar**

**uncompress TISAavg_data7_3_warlock_R4-XXX.tar.Z**

**tar xvf TISAavg_data7_3_warlock_R4-XXX.tar**

**On Linux Cluster:**

**uncompress TISAavg_data7_1_cluster_R4-XXX.tar.Z**

**tar xvf TISAavg_data7_1_cluster_R4-XXX.tar**

**uncompress TISAavg_data7_2_cluster_R4-XXX.tar.Z**

**tar xvf TISAavg_data7_2_cluster_R4-XXX.tar**

**uncompress TISAavg_data7_3_cluster_R4-XXX.tar.Z**

**tar xvf TISAavg_data7_3_cluster_R4-XXX.tar**

15. For **Subsystem 8**, uncompress and untar the tar files by replacing
    **XXX** with the appropriate SCCR number and typing the following
    commands:

**uncompress TISAavg_anc_R4-XXX.tar.Z**

**tar xvf TISAavg_anc_R4-XXX.tar**

**uncompress TISAavg_src_R4-XXX.tar.Z**

**tar xvf TISAavg_src_R4-XXX.tar**

**uncompress TISAavg_src_8.2_R4-XXX.tar.Z**

**tar xvf TISAavg_src_8.2_R4-XXX.tar**

**uncompress TISAavg_data8_1_R4-XXX.tar.Z**

**tar xvf TISAavg_data8_1_R4-XXX.tar**

**uncompress TISAavg_data8_2_R4-XXX.tar.Z**

**tar xvf TISAavg_data8_2_R4-XXX.tar**

**uncompress TISAavg_data8_3_R4-XXX.tar.Z**

**tar xvf TISAavg_data8_3_R4-XXX.tar**

**uncompress TISAavg_data8_4_R4-XXX.tar.Z**

**tar xvf TISAavg_data8_4_R4-XXX.tar**

16. For **Subsystem 10**, uncompress and untar the tar files by
    replacing **XXX** with the appropriate SCCR number and typing the
    following commands:

**source \$CERESENV**

**cd \$CERESHOME**

**uncompress TISAavg_src1_R4-XXX.tar.Z**

**tar xvf TISAavg_src1_R4-XXX.tar**

**uncompress TISAavg_src2_R4-XXX.tar.Z**

**tar xvf TISAavg_src2_R4-XXX.tar**

**uncompress TISAavg_data10_1_R4-XXX.tar.Z**

**tar xvf TISAavg_data10_1_R4-XXX.tar**

**uncompress TISAavg_data10_2_R4-XXX.tar.Z**

**tar xvf TISAavg_data10_2_R4-XXX.tar**

**uncompress TISAavg_data10_3_R4-XXX.tar.Z**

**tar xvf TISAavg_data10_3_R4-XXX.tar**

17. Directory - Files/Direction

**NOTE:** If the PMOA files are not included in the delivery, then skip
this step.

Since PMOA files are delivered, the above PMOA files are required to be
moved to this\
directory:

**\$CERESHOME/tisa_grid/data/out_comp/data/PMOA**

## Compilation

1.  For **Subsystem 7.1, Subsystem 8**, and **Subsystem 10** create the
    message files and message include files:

> **source \$CERESENV**
>
> **cd \$CERESHOME/tisa_avg/smf**
>
> **\$CERESLIB/bin/smfcompile_all.csh**
>
> The smfcompile_all.csh will send a message to the screen at completion
> to indicate whether or not the compile was successful. ASDC personnel
> may have an alternate procedure for compiling these message files. Any
> alternate procedure should copy all message include files to the
> \$PGSINC directory and all message files to the \$PGSMSG directory.

18. For **Subsystem 10** only for PGE **CER10.1P1, webplot.exe,** the
    executable for creating binary data files and converting to .gif
    files for web plotting for **Subsystem 10,** is not provided in the
    tar file. To create the executable in directory
    **\$CERESHOME/tisa_avg/web/plot/dat**, type the following commands:

> **source \$CERESENV**
>
> **cd \$CERESHOME/tisa_avg/web/plot/dat**
>
> **make -f makeplot**

**NOTE:** The executable, webplot.exe, is run during processing of
Subsystem 10, so the above steps must be done before running Subsystem
10.

19. For the **Subsystem 7.1** Main Processor, **tisa7.exe,** the
    executable for the **Subsystem 7.1** Main Processor, is not provided
    in the tar file. To create the executable in directory
    **\$CERESHOME/tisa_avg/bin**, type the following commands:

> **source \$CERESENV**
>
> **cd \$CERESHOME/tisa_avg/src**
>
> **./compile_ss7.csh**

20. For the **Subsystem 8** Main Processor, **tisa8.exe,** the
    executable for the **Subsystem 8** Main Processor is not provided in
    the tar file. To create the executable in directory
    **\$CERESHOME/tisa_avg/bin**, type the following commands:

> **source \$CERESENV**
>
> **cd \$CERESHOME/tisa_avg/src**
>
> **./compile_ss8.csh**

21. For the **Subsystem 8** **SYN Plot** Processor, s**yn_plots.exe,**
    the executable for the **Subsystem 8 SYN plot** Processor is not
    provided in the tar file. To create the executable in directory
    **\$CERESHOME/tisa_avg/bin**, type the following commands:

**cd \$CERESHOME/tisa_avg/bin**

**./compile_8.2P1.csh**

22. For the **Subsystem 10** CERES Clear-sky and Snow/Ice Maps Main
    Processor (PGE CER10.1P2 or CER10.1P5), the executable
    **tisa10_phase1.exe** or **tisa10_aqua_phase1.exe** is not provided
    in the tar file. To create the executable in directory
    \$CERESHOME/tisa_avg/bin, type the following commands:

> **cd \$CERESHOME/tisa_avg/src**
>
> **./compile_ss10_phase1.csh**

23. For the **Subsystem 10** Main Processors (PGEs **CER10.1P1** or
    **CER10.1P4**), the executable **tisa10.CER10.1P1.exe** or
    **tisa10.CER10.1P4.exe** is not provided in the tar file. To create
    the executable in directory **\$CERESHOME/tisa_avg/bin**, type the
    following commands:

> **cd \$CERESHOME/tisa_avg/src**
>
> **./compile_ss10.csh**

24. For **Subsystem 8, comp8.exe** is the executable generating ascii
    files for comparison purposes. To create the executable in directory
    **\$CERESHOME/tisa_avg/test_suites/CER8.1P1**, type the following
    commands:

> **cd \$CERESHOME/tisa_avg/test_suites/CER8.1P1**
>
> **make -f makecmp_8**

25. For **Subsystem 10** PGE **CER10.1P1, comp10.exe** is the executable
    generating binary files for comparison purposes. To create the
    executable in directory
    **\$CERESHOME/tisa_avg/test_suites/CER10.1P1**, type the following
    commands:

> **cd \$CERESHOME/tisa_avg/test_suites/CER10.1P1**
>
> **make -f makecmp_10**

26. For **Subsystem 10** PGE **CER10.1P4, comp10.exe** is the executable
    generating binary files for comparison purposes. To create the
    executable in directory
    **\$CERESHOME/tisa_avg/test_suites/CER10.1P4**, type the following
    commands:

> **cd \$CERESHOME/tisa_avg/test_suites/CER10.1P4**
>
> **make -f makecmp_10**

27. For **Subsystem 10** PGE **CER10.1P3, comp10.exe** is the executable
    generating binary files for comparison purposes. To create the
    executable in directory
    **\$CERESHOME/tisa_avg/test_suites/CER10.1P3**, type the following
    commands:

> **cd \$CERESHOME/tisa_avg/test_suites/CER10.1P3**
>
> **make -f makecmp_10**

# Test and Evaluation Procedures 

This section provides general information on how to execute Subsystem
10.0 and provides an overview of the test and evaluation procedures. It
includes a description of what is being tested and the order in which
the tests should be performed.

## CER7.1.1P1 Main Processor for Subsystem 7.1

### Stand-alone Test Procedures for Terra FM1

#### PCF Generator

The Main Processor production script, **CER7.1.1P1**, references a
Process Control File (PCF) which contain the correct file names and
paths for the test procedures. The PCF file for the test case is created
by first executing an ASCII file generator,
**tisavg_7.1.1P1_ascii_gen_ssit.csh**, and then executing the PCF
generator, **tisavg_7.1.1P1_pcfgen.csh**.

For production run, the ASCII file generator,
**tisavg_7.1.1P1_ascii_gen.csh**, must be executed to create the ASCII
input file for a particular production run. The ASCII file generator
requires four command-line arguments: 1-digit Subsystem Number(7);
4-digit Data Year(1998); 2-digit Data Month(01); and 1-character GGEO
data file exist flag(Y), (Optional, default value = Y). The PCF
generator, **tisavg_7.1.1P1_pcfgen.csh**, then executes using the newly
created ASCII input file name as a command-line argument.

> **NOTE:** The PCF generator script, **tisavg_7.1.1P1_pcfgen.csh**,
> uses the file PCF.template. Therefore, PCF.template must exist in the
> \$CERESHOME/tisa_avg/bin directory.

1.  Generate the ASCII input file for the test case:

> **cd \$CERESHOME/tisa_avg/bin**
>
> **source \$CERESENV**
>
> **source \$CERESHOME/tisa_avg/bin/setup_test-env.csh FM1**
>
> **source \$CERESHOME/tisa_avg/bin/ENV7.1.1P1-env.csh**
>
> **setenv year 2002**
>
> **setenv month 07**
>
> **setenv DATADATE 200207**
>
> **setenv INSTANCE Terra-FM1-MODIS_SSIT_000000.\$DATADATE**
>
> **\$CERESHOME/tisa_avg/bin/tisavg_7.1.1P1_ascii_gen_ssit.csh 7 \$year
> \$month Y**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/:**

-   CER7.1.1P1_PCFin\_\$INSTANCE

28. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_7.1.1P1_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER7.1.1P1_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER7.1.1P1_PCF\_\$INSTANCE

#### Execution

The production script is executed by typing the script name,
**CER7.1.1P1**, followed by three command-line arguments: year (YYYY),
month (MM), and PCF file name.

> **\$CERESHOME/tisa_avg/bin/CER7.1.1P1 \$year \$month
> CER7.1.1P1_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER7.1.1P1, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/data_7/out_comp**:

-   CER_TSIB\_\$INSTANCE\\Zi\*

-   CER_TSIB\_\$INSTANCE\\Zi\*.met

-   CER_JRGRP\_\$INSTANCE

-   CER_JRGRP\_\$INSTANCE.met

-   CER_JVREG\_\$INSTANCE

-   CER_JVREG\_\$INSTANCE.met

\*i indicates multiple files which, for the test case, range from 052 -
054.

#### Exit Codes

The processor CER7.1.1P1 terminates using the CERES-defined EXIT CODES
for the Langley TRMM Information System (LaTIS). Successful completion
is indicated by an exit code of 0.

Failure is indicated by an exit code 202.

#### Main Processor Test Summary

[]{#__RefHeading___Toc188179457 .anchor}Table 3‑1. Test Summary for PGE
7.1.1P1

+-----------------------------+-------------------+-------------------+
|                             | > Warlock         | > Linux Cluster   |
+-----------------------------+-------------------+-------------------+
|                             | > **FM1**         | > **FM1**         |
+-----------------------------+-------------------+-------------------+
| > Run Time                  | > 10:47 minutes   | > 2:38 minutes    |
+-----------------------------+-------------------+-------------------+
| > Memory                    | > 84112 K         | > 1364 K          |
+-----------------------------+-------------------+-------------------+
| > Required Disk Space       | > 2.5 GB          | > 2.5 GB          |
+-----------------------------+-------------------+-------------------+

### Evaluation Procedures

When running the production script, **CER7.1.1P1**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER7.1.1P1_LogReport\_\$INSTANCE, is
located in directory \$CERESHOME/tisa_avg/data/data_7/runlogs.

#### Metadata

Metadata files which end in extension, '.met', are located in the same
directory as their corresponding output files after CER7.1.1P1 has been
executed.

#### Execution of Comparison Software

Due to the size of the output of SS7.1 (307 megabytes), only three of
the 180 files is being delivered in this package; however, the rest will
be provided if requested. The evaluation software for SS7.1 does a diff
on the one file in out_exp and the first file created during processing:

> **cmp
> \$CERESHOME/tisa_avg/data/data_7/out_exp/CER_TSIB\_\$INSTANCE'Zi\*'
> \$CERESHOME/tisa_avg/data/data_7/out_comp/CER_TSIB\_\$INSTANCE'Zi\*'**
>
> \*i indicates multiple files which, for the test case, range from 052
> -054.

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script, which removes PGE
    created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To use the clean-up files for
    **CER7.1.1P1**:

> **\$CERESHOME/tisa_avg/bin/cleanup 7.1.1P1 \$year\$month**

29. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

### Stand-alone Test Procedures for Terra FM2

#### PCF Generator

The Main Processor production script, **CER7.1.1P1**, references a
Process Control File (PCF) which contain the correct file names and
paths for the test procedures. The PCF file for the test case is created
by first executing an ASCII file generator,
**tisavg_7.1.1P1_ascii_gen_ssit.csh**, and then executing the PCF
generator, **tisavg_7.1.1P1_pcfgen.csh**.

For production run, the ASCII file generator,
**tisavg_7.1.1P1_ascii_gen.csh**, must be executed to create the ASCII
input file for a particular production run. The ASCII file generator
requires four command-line arguments: 1-digit Subsystem Number(7);
4-digit Data Year(1998); 2-digit Data Month(01); and 1-character GGEO
data file exist flag(Y), (Optional, default value = Y). The PCF
generator, **tisavg_7.1.1P1_pcfgen.csh**, then executes using the newly
created ASCII input file name as a command-line argument.

> **NOTE:** The PCF generator script, **tisavg_7.1.1P1_pcfgen.csh**,
> uses the file PCF.template. Therefore, PCF.template must exist in the
> \$CERESHOME/tisa_avg/bin directory.

1.  Generate the ASCII input file for the test case:

> **cd \$CERESHOME/tisa_avg/bin**
>
> **source \$CERESENV**
>
> **source \$CERESHOME/tisa_avg/bin/setup_test-env.csh FM2**
>
> **source \$CERESHOME/tisa_avg/bin/ENV7.1.1P1-env.csh**
>
> **setenv year 2001**
>
> **setenv month 10**
>
> **setenv DATADATE 200110**
>
> **setenv INSTANCE Terra-FM2-MODIS_SSIT_000000.\$DATADATE**
>
> **\$CERESHOME/tisa_avg/bin/tisavg_7.1.1P1_ascii_gen_ssit.csh 7 \$year
> \$month Y**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/:**

-   CER7.1.1P1_PCFin\_\$INSTANCE

30. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_7.1.1P1_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER7.1.1P1_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER7.1.1P1_PCF\_\$INSTANCE

#### Execution

The production script is executed by typing the script name,
**CER7.1.1P1**, followed by three command-line arguments: year (YYYY),
month (MM), and PCF file name.

> **\$CERESHOME/tisa_avg/bin/CER7.1.1P1 \$year \$month
> CER7.1.1P1_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER7.1.1P1, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/data_7/out_comp**:

-   CER_TSIB\_\$INSTANCE\\Zi\*

-   CER_TSIB\_\$INSTANCE\\Zi\*.met

-   CER_JRGRP\_\$INSTANCE

-   CER_JRGRP\_\$INSTANCE.met

-   CER_JVREG\_\$INSTANCE

-   CER_JVREG\_\$INSTANCE.met

\*i indicates multiple files which, for the test case, range from 052 -
054.

#### Exit Codes

The processor CER7.1.1P1 terminates using the CERES-defined EXIT CODES
for the Langley TRMM Information System (LaTIS). Successful completion
is indicated by an exit code of 0.

Failure is indicated by an exit code 202.

#### Main Processor Test Summary

[]{#__RefHeading___Toc188179458 .anchor}Table 3‑2. Test Summary for PGE
7.1.1P1

+-----------------------------+-------------------+-------------------+
|                             | > Warlock         | > Linux Cluster   |
+-----------------------------+-------------------+-------------------+
|                             | > **FM2**         | > **FM2**         |
+-----------------------------+-------------------+-------------------+
| > Run Time                  | > 9:17 minutes    | > 2:25 minutes    |
+-----------------------------+-------------------+-------------------+
| > Memory                    | > 84112 K         | > 1364 K          |
+-----------------------------+-------------------+-------------------+
| > Required Disk Space       | > 2.5 GB          | > 2.5 GB          |
+-----------------------------+-------------------+-------------------+

### Evaluation Procedures

When running the production script, **CER7.1.1P1**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER7.1.1P1_LogReport\_\$INSTANCE, is
located in directory \$CERESHOME/tisa_avg/data/data_7/runlogs.

#### Metadata

Metadata files which end in extension, '.met', are located in the same
directory as their corresponding output files after CER7.1.1P1 has been
executed.

#### Execution of Comparison Software

Due to the size of the output of SS7.1 (307 megabytes), only three of
the 180 files is being delivered in this package; however, the rest will
be provided if requested. The evaluation software for SS7.1 does a diff
on the one file in out_exp and the first file created during processing:

> **cmp
> \$CERESHOME/tisa_avg/data/data_7/out_exp/CER_TSIB\_\$INSTANCE'Zi\*'
> \$CERESHOME/tisa_avg/data/data_7/out_comp/CER_TSIB\_\$INSTANCE'Zi\*'**
>
> \*i indicates multiple files which, for the test case, range from 052
> -054.

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script, which removes PGE
    created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To use the clean-up files for
    **CER7.1.1P1**:

> **\$CERESHOME/tisa_avg/bin/cleanup 7.1.1P1 \$year\$month**

31. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

### Stand-alone Test Procedures for Aqua FM3

#### PCF Generator

The Main Processor production script, **CER7.1.1P1**, references a
Process Control File (PCF) which contain the correct file names and
paths for the test procedures. The PCF file for the test case is created
by first executing an ASCII file generator,
**tisavg_7.1.1P1_ascii_gen_ssit.csh**, and then executing the PCF
generator, **tisavg_7.1.1P1_pcfgen.csh**.

For production run, the ASCII file generator,
**tisavg_7.1.1P1_ascii_gen.csh**, must be executed to create the ASCII
input file for a particular production run. The ASCII file generator
requires four command-line arguments: 1-digit Subsystem Number(7);
4-digit Data Year(1998); 2-digit Data Month(01); and 1-character GGEO
data file exist flag(Y), (Optional, default value = Y). The PCF
generator, **tisavg_7.1.1P1_pcfgen.csh**, then executes using the newly
created ASCII input file name as a command-line argument.

> **NOTE:** The PCF generator script, **tisavg_7.1.1P1_pcfgen.csh**,
> uses the file PCF.template. Therefore, PCF.template must exist in the
> \$CERESHOME/tisa_avg/bin directory.

1.  Generate the ASCII input file for the test case:

> **cd \$CERESHOME/tisa_avg/bin**
>
> **source \$CERESENV**
>
> **source \$CERESHOME/tisa_avg/bin/setup_test-env.csh FM3**
>
> **source \$CERESHOME/tisa_avg/bin/ENV7.1.1P1-env.csh**
>
> **setenv year 2002**
>
> **setenv month 07**
>
> **setenv DATADATE 200207**
>
> **setenv INSTANCE Aqua-FM3-MODIS_SSIT_000000.\$DATADATE**
>
> **\$CERESHOME/tisa_avg/bin/tisavg_7.1.1P1_ascii_gen_ssit.csh 7 \$year
> \$month Y**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/:**

-   CER7.1.1P1_PCFin\_\$INSTANCE

32. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_7.1.1P1_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER7.1.1P1_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER7.1.1P1_PCF\_\$INSTANCE

#### Execution

The production script is executed by typing the script name,
**CER7.1.1P1**, followed by three command-line arguments: year (YYYY),
month (MM), and PCF file name.

> **\$CERESHOME/tisa_avg/bin/CER7.1.1P1 \$year \$month
> CER7.1.1P1_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER7.1.1P1, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/data_7/out_comp**:

-   CER_TSIB\_\$INSTANCE\\Zi\*

-   CER_TSIB\_\$INSTANCE\\Zi\*.met

-   CER_JRGRP\_\$INSTANCE

-   CER_JRGRP\_\$INSTANCE.met

-   CER_JVREG\_\$INSTANCE

-   CER_JVREG\_\$INSTANCE.met

\*i indicates multiple files which, for the test case, range from 052 -
054.

#### Exit Codes

The processor CER7.1.1P1 terminates using the CERES-defined EXIT CODES
for the Langley TRMM Information System (LaTIS). Successful completion
is indicated by an exit code of 0.

Failure is indicated by an exit code 202.

#### Main Processor Test Summary

[]{#__RefHeading___Toc188179459 .anchor}Table 3‑3. Test Summary for PGE
7.1.1P1

+-----------------------------+-------------------+-------------------+
|                             | > Warlock         | > Linux Cluster   |
+-----------------------------+-------------------+-------------------+
|                             | > **FM3**         | > **FM3**         |
+-----------------------------+-------------------+-------------------+
| > Run Time                  | > 10:41 minutes   | > 2:27 minutes    |
+-----------------------------+-------------------+-------------------+
| > Memory                    | > 84112 K         | > 1364 K          |
+-----------------------------+-------------------+-------------------+
| > Required Disk Space       | > 2.5 GB          | > 2.5 GB          |
+-----------------------------+-------------------+-------------------+

### Evaluation Procedures

When running the production script, **CER7.1.1P1**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER7.1.1P1_LogReport\_\$INSTANCE, is
located in directory \$CERESHOME/tisa_avg/data/data_7/runlogs.

#### Metadata

Metadata files which end in extension, '.met', are located in the same
directory as their corresponding output files after CER7.1.1P1 has been
executed.

#### Execution of Comparison Software

Due to the size of the output of SS7.1 (307 megabytes), only three of
the 180 files is being delivered in this package; however, the rest will
be provided if requested. The evaluation software for SS7.1 does a diff
on the one file in out_exp and the first file created during processing:

> **cmp
> \$CERESHOME/tisa_avg/data/data_7/out_exp/CER_TSIB\_\$INSTANCE'Zi\*'
> \$CERESHOME/tisa_avg/data/data_7/out_comp/CER_TSIB\_\$INSTANCE'Zi\*'**
>
> \*i indicates multiple files which, for the test case, range from 052
> -054.

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script, which removes PGE
    created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To use the clean-up files for
    **CER7.1.1P1**:

> **\$CERESHOME/tisa_avg/bin/cleanup 7.1.1P1 \$year\$month**

33. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

### Stand-alone Test Procedures for Aqua FM4

#### PCF Generator

The Main Processor production script, **CER7.1.1P1**, references a
Process Control File (PCF) which contain the correct file names and
paths for the test procedures. The PCF file for the test case is created
by first executing an ASCII file generator,
**tisavg_7.1.1P1_ascii_gen_ssit.csh**, and then executing the PCF
generator, **tisavg_7.1.1P1_pcfgen.csh**.

For production run, the ASCII file generator,
**tisavg_7.1.1P1_ascii_gen.csh**, must be executed to create the ASCII
input file for a particular production run. The ASCII file generator
requires four command-line arguments: 1-digit Subsystem Number(7);
4-digit Data Year(1998); 2-digit Data Month(01); and 1-character GGEO
data file exist flag(Y), (Optional, default value = Y). The PCF
generator, **tisavg_7.1.1P1_pcfgen.csh**, then executes using the newly
created ASCII input file name as a command-line argument.

> **NOTE:** The PCF generator script, **tisavg_7.1.1P1_pcfgen.csh**,
> uses the file PCF.template. Therefore, PCF.template must exist in the
> \$CERESHOME/tisa_avg/bin directory.

1.  Generate the ASCII input file for the test case:

> **cd \$CERESHOME/tisa_avg/bin**
>
> **source \$CERESENV**
>
> **source \$CERESHOME/tisa_avg/bin/setup_test-env.csh FM4**
>
> **source \$CERESHOME/tisa_avg/bin/ENV7.1.1P1-env.csh**
>
> **setenv year 2002**
>
> **setenv month 07**
>
> **setenv DATADATE 200207**
>
> **setenv INSTANCE Aqua-FM4-MODIS_SSIT_000000.\$DATADATE**
>
> **\$CERESHOME/tisa_avg/bin/tisavg_7.1.1P1_ascii_gen_ssit.csh 7 \$year
> \$month Y**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/:**

-   CER7.1.1P1_PCFin\_\$INSTANCE

34. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_7.1.1P1_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER7.1.1P1_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER7.1.1P1_PCF\_\$INSTANCE

#### Execution

The production script is executed by typing the script name,
**CER7.1.1P1**, followed by three command-line arguments: year (YYYY),
month (MM), and PCF file name.

> **\$CERESHOME/tisa_avg/bin/CER7.1.1P1 \$year \$month
> CER7.1.1P1_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER7.1.1P1, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/data_7/out_comp**:

-   CER_TSIB\_\$INSTANCE\\Zi\*

-   CER_TSIB\_\$INSTANCE\\Zi\*.met

-   CER_JRGRP\_\$INSTANCE

-   CER_JRGRP\_\$INSTANCE.met

-   CER_JVREG\_\$INSTANCE

-   CER_JVREG\_\$INSTANCE.met

\*i indicates multiple files which, for the test case, range from 052 -
054.

#### Exit Codes

The processor CER7.1.1P1 terminates using the CERES-defined EXIT CODES
for the Langley TRMM Information System (LaTIS). Successful completion
is indicated by an exit code of 0.

Failure is indicated by an exit code 202.

#### Main Processor Test Summary

[]{#__RefHeading___Toc188179460 .anchor}Table 3‑4. Test Summary for PGE
7.1.1P1

+-----------------------------+-------------------+-------------------+
|                             | > Warlock         | > Linux Cluster   |
+-----------------------------+-------------------+-------------------+
|                             | > **FM4**         | > **FM4**         |
+-----------------------------+-------------------+-------------------+
| > Run Time                  | > 10:09 minutes   | > 2:29 minutes    |
+-----------------------------+-------------------+-------------------+
| > Memory                    | > 84112 K         | > 1364 K          |
+-----------------------------+-------------------+-------------------+
| > Required Disk Space       | > 2.5 GB          | > 2.5 GB          |
+-----------------------------+-------------------+-------------------+

### Evaluation Procedures

When running the production script, **CER7.1.1P1**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER7.1.1P1_LogReport\_\$INSTANCE, is
located in directory \$CERESHOME/tisa_avg/data/data_7/runlogs.

#### Metadata

Metadata files which end in extension, '.met', are located in the same
directory as their corresponding output files after CER7.1.1P1 has been
executed.

#### Execution of Comparison Software

Due to the size of the output of SS7.1 (307 megabytes), only three of
the 180 files is being delivered in this package; however, the rest will
be provided if requested. The evaluation software for SS7.1 does a diff
on the one file in out_exp and the first file created during processing:

> **cmp
> \$CERESHOME/tisa_avg/data/data_7/out_exp/CER_TSIB\_\$INSTANCE'Zi\*'
> \$CERESHOME/tisa_avg/data/data_7/out_comp/CER_TSIB\_\$INSTANCE'Zi\*'**
>
> \*i indicates multiple files which, for the test case, range from 052
> -054.

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script, which removes PGE
    created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To use the clean-up files for
    **CER7.1.1P1**:

> **\$CERESHOME/tisa_avg/bin/cleanup 7.1.1P1 \$year\$month**

35. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

## CER8.1P1 Main Processor

### Stand Alone Test Procedures for Terra FM1

#### PCF Generator

The Main Processor production script, **CER8.1P1**, references a Process
Control File (PCF) which contain the correct file names and paths for
the test procedures. The PCF for the test case is created by first
executing an ASCII file generator, **tisavg_8.1P1_ascii_gen_test**, and
then executing the PCF generator, **tisavg_8.1P1_pcfgen.csh**.

For production runs, the ASCII file generator, tisavg_8.1P1_ascii_gen,
must be executed to create the ASCII input file for a particular
production run. The ASCII file generator requires four command line
arguments, 1 or 2-digit subsystem number, 4-digit Data Year, 2-digit
Data Month. The PCF generator, tisavg_8.1P1_pcfgen.csh, is then executed
using the newly created ASCII input file name as a command line
argument.

> **NOTE**: The PCF generator script, **tisavg_8.1P1_pcfgen.csh**, uses
> the file PCF.template. Therefore, PCF.template must exist in the same
> directory.

1.  Generate the ASCII input file for the test case:

**cd \$CERESHOME/tisa_avg/bin**

**source \$CERESENV**

**source \$CERESHOME/tisa_avg/bin/setup_test_env_Terra_FM1.csh**

**source \$CERESHOME/tisa_avg/bin/ENV8.1P1-env.csh**

**setenv year 2001**

**setenv month 07**

**setenv DATADATE 200107**

**setenv INSTANCE Terra-FM1-MODIS_SSIT_000000.\$DATADATE**

**\$CERESHOME/tisa_avg/bin/tisavg_8.1P1_ascii_gen_test.csh 8 \$year
\$month**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER8.1P1_PCFin\_\$INSTANCE

36. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_8.1P1_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER8.1P1_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER8.1P1_PCF\_\$INSTANCE

#### Execution

The production script is executed by typing the script name,
**CER8.1P1**, followed by three command-line arguments: year (YYYY),
month (MM), and PCF file name.

> **\$CERESHOME/tisa_avg/bin/CER8.1P1 \$year \$month
> CER8.1P1_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER_8.1P1, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/data_8/out_comp**:

-   CER_AVG\_\$INSTANCE

-   CER_AVG\_\$INSTANCE.met

-   CER_ZAVG\_\$INSTANCE

-   CER_ZAVG\_\$INSTANCE.met

-   CER_SYN\_\$INSTANCE\\i\*

-   CER_SYN\_\$INSTANCE\\i\*.met

-   CER_LRGRP\_\$INSTANCE

-   CER_LRGRP\_\$INSTANCE.met

\*i indicates multiple day files which, for the test case, range from
01-31.

#### Exit Codes

All **CER8.1P1 software terminates using the CERES defined EXIT CODES**
for the Langley TRMM Information System (LaTIS). Successful completions
indicated by an exit code of 0.

#### Main Processor Test Summary

> Total Run Time: 1 hours 15 minutes and 45 seconds
>
> Memory: 242224 K
>
> Required Disk Space: 19.08 GB

### Evaluation Procedures

When running the production script, **CER8.1P1**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER8.1P1_LogReport\_\$INSTANCE is located
in directory \$CERESHOME/tisa_avg/data/data_8/runlogs.

#### Metadata

Metadata files which end in extension,'.met', are located in the same
directory as their corresponding output files after CER8.1P1 has been
executed.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_8/out_exp and new input files from the
execution are in \$CERESHOME/tisa_avg/data/data_8/out_comp. These input
files are accessed from those areas for the comparison.

**eval_ss8_output_Terra_FM1.csh** is a script needed to execute the
comparison program. Type the following:

> **cd \$CERESHOME/tisa_avg/test_suites/CER8.1P1**
>
> **eval_ss8_output_Terra_FM1.csh**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script, which removes PGE
    created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To use the clean-up files for
    **CER8.1P1**:

> **\$CERESHOME/tisa_avg/bin/cleanup 8.1P1 \$year\$month**

37. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

### Stand Alone Test Procedures for Terra FM2

#### PCF Generator

The Main Processor production script, **CER8.1P1**, references a Process
Control File (PCF) which contain the correct file names and paths for
the test procedures. The PCF for the test case is created by first
executing an ASCII file generator, **tisavg_8.1P1_ascii_gen_test**, and
then executing the PCF generator, **tisavg_8.1P1_pcfgen.csh**.

For production runs, the ASCII file generator, tisavg_8.1P1_ascii_gen,
must be executed to create the ASCII input file for a particular
production run. The ASCII file generator requires four command line
arguments, 1 or 2-digit subsystem number, 4-digit Data Year, 2-digit
Data Month. The PCF generator, tisavg_8.1P1_pcfgen.csh, is then executed
using the newly created ASCII input file name as a command line
argument.

> **NOTE**: The PCF generator script, **tisavg_8.1P1_pcfgen.csh**, uses
> the file PCF.template. Therefore, PCF.template must exist in the same
> directory.

1.  Generate the ASCII input file for the test case:

**cd \$CERESHOME/tisa_avg/bin**

**source \$CERESENV**

**source \$CERESHOME/tisa_avg/bin/setup_test_env_Terra_FM2.csh**

**source \$CERESHOME/tisa_avg/bin/ENV8.1P1-env.csh**

**setenv year 2001**

**setenv month 08**

**setenv DATADATE 200108**

**setenv INSTANCE Terra-FM2-MODIS_SSIT_000000.\$DATADATE**

**\$CERESHOME/tisa_avg/bin/tisavg_8.1P1_ascii_gen_test.csh 8 \$year
\$month**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER8.1P1_PCFin\_\$INSTANCE

38. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_8.1P1_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER8.1P1_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER8.1P1_PCF\_\$INSTANCE

#### Execution

The production script is executed by typing the script name,
**CER8.1P1**, followed by three command-line arguments: year (YYYY),
month (MM), and PCF file name.

> **\$CERESHOME/tisa_avg/bin/CER8.1P1 \$year \$month
> CER8.1P1_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER_8.1P1, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/data_8/out_comp**:

-   CER_AVG\_\$INSTANCE

-   CER_AVG\_\$INSTANCE.met

-   CER_ZAVG\_\$INSTANCE

-   CER_ZAVG\_\$INSTANCE.met

-   CER_SYN\_\$INSTANCE\\i\*

-   CER_SYN\_\$INSTANCE\\i\*.met

-   CER_LRGRP\_\$INSTANCE

-   CER_LRGRP\_\$INSTANCE.met

\*i indicates multiple day files which, for the test case, range from
01-31.

#### Exit Codes

All **CER8.1P1 software terminates using the CERES defined EXIT CODES**
for the Langley TRMM Information System (LaTIS). Successful completions
indicated by an exit code of 0.

#### Main Processor Test Summary

> Total Run Time: 1 hours 15 minutes and 45 seconds
>
> Memory: 242224 K
>
> Required Disk Space: 19.08 GB

### Evaluation Procedures

When running the production script, **CER8.1P1**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER8.1P1_LogReport\_\$INSTANCE is located
in directory \$CERESHOME/tisa_avg/data/data_8/runlogs.

#### Metadata

Metadata files which end in extension,'.met', are located in the same
directory as their corresponding output files after CER8.1P1 has been
executed.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_8/out_exp and new input files from the
execution are in \$CERESHOME/tisa_avg/data/data_8/out_comp. These input
files are accessed from those areas for the comparison.

**eval_ss8_output_Terra_FM2.csh** is a script needed to execute the
comparison program. Type the following:

> **cd \$CERESHOME/tisa_avg/test_suites/CER8.1P1**
>
> **eval_ss8_output_Terra_FM2.csh**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script, which removes PGE
    created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To use the clean-up files for
    **CER8.1P1**:

> **\$CERESHOME/tisa_avg/bin/cleanup 8.1P1 \$year\$month**

39. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

## CER8.2P1 Post Processor

### Stand Alone Test Procedures for Terra FM1

#### PCF Generator

The Post Processor production script, **CER8.2P1**, references a Process
Control File (PCF) which contain the correct file names and paths for
the test procedures. The PCF for the test case is created by first
executing an ASCII file generator, **tisavg_8.2P1_ascii_gen_test**, and
then executing the PCF generator, **tisavg_8.2P1_pcfgen.csh**.

For production runs, the ASCII file generator, tisavg_8.2P1_ascii_gen,
must be executed to create the ASCII input file for a particular
production run. The ASCII file generator requires two command line
arguments, 4-digit Data Year, 2-digit Data Month. The PCF generator,
tisavg_8.2P1_pcfgen.csh, is then executed using the newly created ASCII
input file name as a command line argument.

> **NOTE**: The PCF generator script, **tisavg_8.2P1_pcfgen.csh**, uses
> the file PCF.template. Therefore, PCF.template must exist in the same
> directory.
>
> **source \$CERESENV**

**set RCFDIR = \$CERESHOME/tisa_avg/rcf**

1.  Generate the ASCII input file for the test case:

**cd \$CERESHOME/tisa_avg/bin**

**source \$CERESHOME/tisa_avg/bin/setup_test_env_Terra_FM1.csh**

**source \$CERESHOME/tisa_avg/bin/ENV8.2P1-env.csh**

**setenv year 2001**

**setenv month 07**

**setenv DATADATE 200107**

**setenv INSTANCE Terra-FM1-MODIS_SSIT_000000.\$DATADATE**

**\$CERESHOME/tisa_avg/bin/cleanup_8.2P1.csh \$year\$month**

**\$CERESHOME/tisa_avg/bin/tisavg_8.2P1_ascii_gen_test.csh \$year
\$month**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER8.2P1_PCFin\_\$INSTANCE

40. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_8.2P1_pcfgen.csh
> \$RCFDIR/CER8.2P1_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER8.2P1_PCF\_\$INSTANCE

#### Execution

The production script is executed by typing the script name,
**CER8.2P1**, followed by three command-line arguments: year (YYYY),
month (MM), and PCF file name.

> **\$CERESHOME/tisa_avg/bin/CER8.2P1 \$year \$month
> \$RCFDIR/CER8.2P1_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER_8.2P1, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/web/plot/gif/SYN_200107 directory**:

-   AER_OPT\_\*.gif

-   ALB_SFC_CLR\_\*.gif

-   CLD_EMISS\_\*.gif

-   CLD_FRAC\_\*.gif

-   CLD_ICE_DIAM\_\*.gif

-   CLD_LIQ_RAD\_\*.gif

-   CLD_OPT\_\*.gif

-   CLD_PBOT\_\*.gif

-   CLD_PHASE\_\*.gif

-   CLD_PTOP\_\*.gif

-   CLD_TEMP\_\*.gif

-   LW_DOWN_SFC\_\*.gif

-   LW_NET_SFC\_\*.gif

-   LW_TOA_CLDFORC\_\*.gif

-   LW_TOA_OBS\_\*.gif

-   LW_TOA_TUN\_\*.gif

-   LW_TOA_UNT-OBS\_\*.gif

-   NET_TOA_OBS\_\*.gif

-   SFC_UV_INDEX\_\*gif

-   SW_DOWN_SFC\_\*.gif

-   SW_NET_SFC\_\*.gif

-   SW_SFC_AERFORC\_\*.gif

-   SW_TOA_AERFORC\_\*.gif

-   SW_TOA_CLDFORC\_\*.gif

-   SW_TOA_OBS\_\*.gif

-   SW_TOA_TUN\_\*.gif

-   SW_TOA_UNT-OBS\_\*.gif

\* files 01 - 248.

#### Exit Codes

All **CER8.2P1 software terminates using the CERES defined EXIT CODES**
for the Langley TRMM Information System (LaTIS). Successful completions
indicated by an exit code of 0.

#### Main Processor Test Summary

> Total Run Time: 6141.997u 1004.770s 2:40:12.41
>
> Memory: 30552 K
>
> Required Disk Space: 1GB

### Evaluation Procedures

When running the production script, **CER8.2P1**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER8.2P1_LogReport\_\$INSTANCE is located
in directory \$CERESHOME/tisa_avg/data/data_8/runlogs.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_8/out_exp and new input files from the
execution are in \$CERESHOME/tisa_avg/data/data_8/int_prod. These input
files are accessed from those areas for the comparison.

**eval_ss8_output_Terra_FM1.csh** is a script needed to execute the
comparison program. Type the following:

> **cd \$CERESHOME/tisa_avg/test_suites/CER8.2P1**
>
> **\$CERESLIB/bin/setVariables.csh test**
>
> **set PCFTest = 1**
>
> **eval_ss8.2_output_Terra_FM1.csh \$PCFTest**
>
> **set LOGTest = 2**
>
> **eval_ss8.2_output_Terra_FM1.csh \$LOGTest**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script, which removes PGE
    created files, **cleanup_8.2P1.csh**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To use the clean-up files for
    **CER8.2P1**:

> **\$CERESHOME/tisa_avg/bin/cleanup_8.2P1.csh \$year\$month**

41. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

### Stand Alone Test Procedures for Terra FM2

#### PCF Generator

The Main Processor production script, **CER8.2P1**, references a Process
Control File (PCF) which contain the correct file names and paths for
the test procedures. The PCF for the test case is created by first
executing an ASCII file generator, **tisavg_8.2P1_ascii_gen_test**, and
then executing the PCF generator, **tisavg_8.2P1_pcfgen.csh**.

For production runs, the ASCII file generator, tisavg_8.2P1_ascii_gen,
must be executed to create the ASCII input file for a particular
production run. The ASCII file generator requires two command line
arguments, 4-digit Data Year, 2-digit Data Month. The PCF generator,
tisavg_8.2P1_pcfgen.csh, is then executed using the newly created ASCII
input file name as a command line argument.

> **NOTE**: The PCF generator script, **tisavg_8.2P1_pcfgen.csh**, uses
> the file PCF.template. Therefore, PCF.template must exist in the same
> directory.

**set RCFDIR = \$CERESHOME/tisa_avg/rcf**

1.  Generate the ASCII input file for the test case:

**cd \$CERESHOME/tisa_avg/bin**

**source \$CERESHOME/tisa_avg/bin/setup_test_env_Terra_FM2.csh**

**source \$CERESHOME/tisa_avg/bin/ENV8.2P1-env.csh**

**setenv year 2001**

**setenv month 08**

**\$CERESHOME/tisa_avg/bin/cleanup_8.2P1.csh \$year\$month**

**setenv DATADATE 200108**

**setenv INSTANCE Terra-FM2-MODIS_SSIT_000000.\$DATADATE**

**\$CERESHOME/tisa_avg/bin/tisavg_8.2P1_ascii_gen_test.csh \$year
\$month**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER8.2P1_PCFin\_\$INSTANCE

42. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_8.2P1_pcfgen.csh
> \$RCFDIR/CER8.2P1_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER8.2P1_PCF\_\$INSTANCE

#### Execution

The production script is executed by typing the script name,
**CER8.2P1**, followed by three command-line arguments: year (YYYY),
month (MM), and PCF file name.

> **\$CERESHOME/tisa_avg/bin/CER8.2P1 \$year \$month
> \$RCFDIR/CER8.2P1_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER_8.2P1, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/web/plot/gif/SYN_200108 directory**:

-   AER_OPT\_\*.gif

-   ALB_SFC_CLR\_\*.gif

-   CLD_EMISS\_\*.gif

-   CLD_FRAC\_\*.gif

-   CLD_ICE_DIAM\_\*.gif

-   CLD_LIQ_RAD\_\*.gif

-   CLD_OPT\_\*.gif

-   CLD_PBOT\_\*.gif

-   CLD_PHASE\_\*.gif

-   CLD_PTOP\_\*.gif

-   CLD_TEMP\_\*.gif

-   LW_DOWN_SFC\_\*.gif

-   LW_NET_SFC\_\*.gif

-   LW_TOA_CLDFORC\_\*.gif

-   LW_TOA_OBS\_\*.gif

-   LW_TOA_TUN\_\*.gif

-   LW_TOA_UNT-OBS\_\*.gif

-   NET_TOA_OBS\_\*.gif

-   SFC_UV_INDEX\_\*gif

-   SW_DOWN_SFC\_\*.gif

-   SW_NET_SFC\_\*.gif

-   SW_SFC_AERFORC\_\*.gif

-   SW_TOA_AERFORC\_\*.gif

-   SW_TOA_CLDFORC\_\*.gif

-   SW_TOA_OBS\_\*.gif

-   SW_TOA_TUN\_\*.gif

-   SW_TOA_UNT-OBS\_\*.gif

\* files 01 - 248.

#### Exit Codes

All **CER8.2P1 software terminates using the CERES defined EXIT CODES**
for the Langley TRMM Information System (LaTIS). Successful completions
indicated by an exit code of 0.

#### Main Processor Test Summary

> Total Run Time: 6141.997u 1004.770s 2:40:12.41
>
> Memory: 30552 K
>
> Required Disk Space: 1 GB

### Evaluation Procedures

When running the production script, **CER8.2P1**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER8.1P1_LogReport\_\$INSTANCE is located
in directory \$CERESHOME/tisa_avg/data/data_8/runlogs.

cd \$CERESHOME/ggeo/test_suites/CER8.2P1

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_8/out_exp and new input files from the
execution are in \$CERESHOME/tisa_avg/data/data_8/out_comp. These input
files are accessed from those areas for the comparison.

**eval_ss8.2_output_Terra_FM2.csh** is a script needed to execute the
comparison program. Type the following:

> **cd \$CERESHOME/tisa_avg/test_suites/CER8.2P1**
>
> **\$CERESLIB/bin/setVariables.csh test**
>
> **set PCFTest = 1**
>
> **eval_ss8.2_output_Terra_FM2.csh \$PCFTest**
>
> **set LOGTest = 2**
>
> **eval_ss8.2_output_Terra_FM2.csh \$LOGTest**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script, which removes PGE
    created files, **cleanup_8.2P1.csh**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To use the clean-up files for
    **CER8.2P1**:

> **\$CERESHOME/tisa_avg/bin/cleanup_8.2P1.csh \$year\$month**

43. Environment variable F90 must be set to the 64-bit SGI F90 compiler

## CER10.1P1 Main Processor

### Stand-alone Test Procedures for Terra FM1

**[(NOTE: CER10.1P2 has to be run before running this test procedure for
Terra.)]{.underline}**

#### PCF Generator

The Main Processor production script, **CER10.1P1,** references a
Process Control File (PCF) which contains the correct file names and
paths for the test procedures. The PCF file for the test case is created
by first executing an ASCII file generator,
**tisavg_10.1P1_ascii_ssit_gen.csh**, and then executing the PCF
generator, **tisavg_10.1P1_pcfgen.csh**. The ASCII file generators
source Subsystem 10.0-specific environment script **ENV10.1P1_env.csh**
and **setup_test_env_Terra_FM1.csh**.

For production runs, the ASCII file generator,
**tisavg_10.1P1_ascii_SSIT_gen.csh**, must be executed to create the
ASCII input file for a particular production run. The ASCII file
generator requires four command-line arguments: 2-digit subsystem
number(10); 4-digit Data Year(1998); 2-digit Data Month(02); and
1-character GGEO data file exist flag(Y), (optional, default value = Y).
The PCF generator, **tisavg_10.1P1_pcfgen.csh,** then must be executed
using the newly created ASCII input file name as a command-line
argument.

**NOTE:** The PCF generator script, **tisavg_10.1P1_pcfgen.csh**, uses
the file PCF.template. Therefore, PCF.template must exist in the same
directory.

1.  Generate the ASCII input file for the test case:

> **cd \$CERESHOME/tisa_avg/bin**
>
> **source \$CERESENV**
>
> **source \$CERESHOME/tisa_avg/bin/setup_test_env_Terra_FM1.csh**
>
> **source \$CERESHOME/tisa_avg/bin/ENV10.1P1-env.csh**
>
> **setenv year 2002**
>
> **setenv month 07**
>
> **setenv DATADATE 200207**
>
> **setenv INSTANCE Terra-FM1-MODIS_SSIT_000000.\$DATADATE**
>
> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P1_ascii_ssit_gen.csh 10 \$year
> \$month Y**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P1_PCFin\_\$INSTANCE

44. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P1_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER10.1P1_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P1_PCF\_\$INSTANCE

#### Execution

Execute the production script by typing the script name, **CER10.1P1**,
followed by three command-line arguments: year (YYYY), month (MM), and
PCF file name.

**\$CERESHOME/tisa_avg/bin/CER10.1P1 \$year \$month
CER10.1P1_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER10.1P1, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/data_10/out_comp**:

-   CER_SRBAVG1\_\$INSTANCE

-   CER_SRBAVG1\_\$INSTANCE.met

-   CER_SRBAVG2\_\$INSTANCE

-   CER_SRBAVG2\_\$INSTANCE.met

-   CER_SRBAVG3\_\$INSTANCE

-   CER_SRBAVG3\_\$INSTANCE.met

-   CER_NQCRP\_\$INSTANCE

-   CER_NQCRP\_\$INSTANCE.met

-   CER_NRGRP\_\$INSTANCE

-   CER_NRGRP\_\$INSTANCE.met

-   CER_NVREG\_\$INSTANCE

-   CER_NVREG\_\$INSTANCE.met

Create the following files in
**\$CERESHOME/tisa_avg/data/ancillary/dynamic:**

-   CER_xglb\_\$INSTANCE

-   CER_xglb\_\$INSTANCE.met

Create the following files in **\$CERESHOME/tisa_avg/web/tsplot:**

-   SURF_TSP\_\$DATADATE\\\_2.pdf

-   TOA_TSP\_\$DATADATE\\\_2.pdf

Create the following files in
**\$CERESHOME/tisa_avg/web/plot/gif/TAVG\_\$DATADATE\\\_2:**

-   CALB_A\_\$DATADATE\\\_2.gif

-   CALB_B\_\$DATADATE\\\_2.gif

-   CALB_D\_\$DATADATE\\\_2.gif

-   CLDO_HIGH\_\$DATADATE\\\_2.gif

-   CLDO_LMID\_\$DATADATE\\\_2.gif

-   CLDO_LOW\_\$DATADATE\\\_2.gif

-   CLDO_UMID\_\$DATADATE\\\_2.gif

-   CLDP_HIGH\_\$DATADATE\\\_2.gif

-   CLDP_LMID\_\$DATADATE\\\_2.gif

-   CLDP_LOW\_\$DATADATE\\\_2.gif

-   CLDP_UMID\_\$DATADATE\\\_2.gif

-   CLW_A\_\$DATADATE\\\_2.gif

-   CLW_B\_\$DATADATE\\\_2.gif

-   CLW_D\_\$DATADATE\\\_2.gif

-   CNF_A\_\$DATADATE\\\_2.gif

-   CNF_B\_\$DATADATE\\\_2.gif

-   CNF_D\_\$DATADATE\\\_2.gif

-   CSDLW_A\_\$DATADATE\\\_2.gif

-   CSDLW_B\_\$DATADATE\\\_2.gif

-   CSDLW_D\_\$DATADATE\\\_2.gif

-   CSDSW_A\_\$DATADATE\\\_2.gif

-   CSDSW_B\_\$DATADATE\\\_2.gif

-   CSDSW_D\_\$DATADATE\\\_2.gif

-   CSDWN_A\_\$DATADATE\\\_2.gif

-   CSNLW_A\_\$DATADATE\\\_2.gif

-   CSNLW_B\_\$DATADATE\\\_2.gif

-   CSNLW_D\_\$DATADATE\\\_2.gif

-   CSNSW_A\_\$DATADATE\\\_2.gif

-   CSNSW_B\_\$DATADATE\\\_2.gif

-   CSNSW_D\_\$DATADATE\\\_2.gif

-   CSN_B\_\$DATADATE\\\_2.gif

-   CSW_A\_\$DATADATE\\\_2.gif

-   CSW_B\_\$DATADATE\\\_2.gif

-   CSW_D\_\$DATADATE\\\_2.gif

-   CWN_A\_\$DATADATE\\\_2.gif

-   CWN_B\_\$DATADATE\\\_2.gif

-   CWN_D\_\$DATADATE\\\_2.gif

-   TALB_A\_\$DATADATE\\\_2.gif

-   TALB_B\_\$DATADATE\\\_2.gif

-   TALB_D\_\$DATADATE\\\_2.gif

-   TLW_A\_\$DATADATE\\\_2.gif

-   TLW_B\_\$DATADATE\\\_2.gif

-   TLW_D\_\$DATADATE\\\_2.gif

-   TNF_A\_\$DATADATE\\\_2.gif

-   TNF_B\_\$DATADATE\\\_2.gif

-   TNF_D\_\$DATADATE\\\_2.gif

-   TSDLW_B\_\$DATADATE\\\_2.gif

-   TSDSW_A\_\$DATADATE\\\_2.gif

-   TSDSW_B\_\$DATADATE\\\_2.gif

-   TSDSW_D\_\$DATADATE\\\_2.gif

-   TSDWN_A\_\$DATADATE\\\_2.gif

-   TSNLW_A\_\$DATADATE\\\_2.gif

-   TSNLW_B\_\$DATADATE\\\_2.gif

-   TSNLW_D\_\$DATADATE\\\_2.gif

-   TSNSW_A\_\$DATADATE\\\_2.gif

-   TSNSW_B\_\$DATADATE\\\_2.gif

-   TSNSW_D\_\$DATADATE\\\_2.gif

-   TSN_B\_\$DATADATE\\\_2.gif

-   TSW_A\_\$DATADATE\\\_2.gif

-   TSW_B\_\$DATADATE\\\_2.gif

-   TSW_D\_\$DATADATE\\\_2.gif

-   TWN_A\_\$DATADATE\\\_2.gif

-   TWN_B\_\$DATADATE\\\_2.gif

-   TWN_D\_\$DATADATE\\\_2.gif

#### Exit Codes

The processor CER10.1P1 terminates using the CERES-defined EXIT CODES
for the Langley TRMM Information System (LaTIS). Successful completion
is indicated by an exit code of 0. Failure is indicated by an exit code
202.

#### Main Processor Test Summary

Total Run Time: 15 minutes 47 seconds

Memory: 132752 K

Required Disk Space: 3.4 GB

### Evaluation Procedures

When running the production script, **CER10.1P1**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER10.1P1_LogReport\_\$INSTANCE, is
located in directory \$CERESHOME/tisa_avg/data/data_10/runlogs.

#### Metadata

Metadata files which end in extension,'.met', are located in the same
directory as their corresponding output files after CER10.1P1 has been
executed. Metadata files are written to directory,
\$CERESHOME/tisa_avg/data/data_10/out_comp.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_10/out_exp and new input files from the
execution are in \$CERESHOME/tisa_avg/data/data_10/out_comp. These input
files are accessed from those areas for the comparison.

**eval_ss10_output_Terra.csh** is a script needed to execute the
comparison program. Type the following:

> **cd \$CERESHOME/tisa_avg/test_suites/CER10.1P1**
>
> **eval_ss10_output_Terra_FM1.csh \$year \$month**
>
> **cmp \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_xglb\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_xglb\_\$INSTANCE**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script which removes
    PGE-created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To clean up the files for **Terra
    FM1** **CER10.1P1**:

> **\$CERESHOME/tisa_avg/bin/cleanup 10.1P1 \$year\$month**

45. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

### Stand-alone Test Procedures for Terra FM2

**[(NOTE: CER10.1P2 has to be run before running this test procedure for
Terra.)]{.underline}**

#### PCF Generator

The Main Processor production script, **CER10.1P1,** references a
Process Control File (PCF) which contains the correct file names and
paths for the test procedures. The PCF file for the test case is created
by first executing an ASCII file generator,
**tisavg_10.1P1_ascii_ssit_gen.csh**, and then executing the PCF
generator, **tisavg_10.1P1_pcfgen.csh**. The ASCII file generators
source Subsystem 10.0-specific environment script **ENV10.1P1_env.csh**
and **setup_test_env_Terra_FM2.csh**.

For production runs, the ASCII file generator,
**tisavg_10.1P1_ascii_ssit_gen.csh**, must be executed to create the
ASCII input file for a particular production run. The ASCII file
generator requires four command-line arguments: 2-digit subsystem
number(10); 4-digit Data Year(1998); 2-digit Data Month(02); and
1-character GGEO data file exist flag(Y), (optional, default value = Y).
The PCF generator, **tisavg_10.1P1_pcfgen.csh,** then must be executed
using the newly created ASCII input file name as a command-line
argument.

**NOTE:** The PCF generator script, **tisavg_10.1P1_pcfgen.csh**, uses
the file PCF.template. Therefore, PCF.template must exist in the same
directory.

1.  Generate the ASCII input file for the test case:

> **cd \$CERESHOME/tisa_avg/bin**
>
> **source \$CERESENV**
>
> **source \$CERESHOME/tisa_avg/bin/setup_test_env_Terra_FM2.csh**
>
> **source \$CERESHOME/tisa_avg/bin/ENV10.1P1-env.csh**
>
> **setenv year 2002**
>
> **setenv month 07**
>
> **setenv DATADATE 200207**
>
> **setenv INSTANCE Terra-FM2-MODIS_SSIT_000000.\$DATADATE**
>
> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P1_ascii_ssit_gen.csh 10 \$year
> \$month Y**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P1_PCFin\_\$INSTANCE

46. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P1_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER10.1P1_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P1_PCF\_\$INSTANCE

#### Execution

Execute the production script by typing the script name, **CER10.1P1**,
followed by three command-line arguments: year (YYYY), month (MM), and
PCF file name.

**\$CERESHOME/tisa_avg/bin/CER10.1P1 \$year \$month
CER10.1P1_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER10.1P1, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/data_10/out_comp**:

-   CER_SRBAVG1\_\$INSTANCE

-   CER_SRBAVG1\_\$INSTANCE.met

-   CER_SRBAVG2\_\$INSTANCE

-   CER_SRBAVG2\_\$INSTANCE.met

-   CER_SRBAVG3\_\$INSTANCE

-   CER_SRBAVG3\_\$INSTANCE.met

-   CER_NQCRP\_\$INSTANCE

-   CER_NQCRP\_\$INSTANCE.met

-   CER_NRGRP\_\$INSTANCE

-   CER_NRGRP\_\$INSTANCE.met

-   CER_NVREG\_\$INSTANCE

-   CER_NVREG\_\$INSTANCE.met

Create the following files in
**\$CERESHOME/tisa_avg/data/ancillary/dynamic:**

-   CER_xglb\_\$INSTANCE

-   CER_xglb\_\$INSTANCE.met

Create the following files in **\$CERESHOME/tisa_avg/web/tsplot:**

-   SURF_TSP\_\$DATADATE\\\_3.pdf

-   TOA_TSP\_\$DATADATE\\\_3.pdf

Create the following files in
**\$CERESHOME/tisa_avg/web/plot/gif/TAVG\_\$DATADATE\\\_3:**

-   CALB_A\_\$DATADATE\\\_3.gif

-   CALB_B\_\$DATADATE\\\_3.gif

-   CALB_D\_\$DATADATE\\\_3.gif

-   CLDO_HIGH\_\$DATADATE\\\_3.gif

-   CLDO_LMID\_\$DATADATE\\\_3.gif

-   CLDO_LOW\_\$DATADATE\\\_3.gif

-   CLDO_UMID\_\$DATADATE\\\_3.gif

-   CLDP_HIGH\_\$DATADATE\\\_3.gif

-   CLDP_LMID\_\$DATADATE\\\_3.gif

-   CLDP_LOW\_\$DATADATE\\\_3.gif

-   CLDP_UMID\_\$DATADATE\\\_3.gif

-   CLW_A\_\$DATADATE\\\_3.gif

-   CLW_B\_\$DATADATE\\\_3.gif

-   CLW_D\_\$DATADATE\\\_3.gif

-   CNF_A\_\$DATADATE\\\_3.gif

-   CNF_B\_\$DATADATE\\\_3.gif

-   CNF_D\_\$DATADATE\\\_3.gif

-   CSDLW_A\_\$DATADATE\\\_3.gif

-   CSDLW_B\_\$DATADATE\\\_3.gif

-   CSDLW_D\_\$DATADATE\\\_3.gif

-   CSDSW_A\_\$DATADATE\\\_3.gif

-   CSDSW_B\_\$DATADATE\\\_3.gif

-   CSDSW_D\_\$DATADATE\\\_3.gif

-   CSDWN_A\_\$DATADATE\\\_3.gif

-   CSNLW_A\_\$DATADATE\\\_3.gif

-   CSNLW_B\_\$DATADATE\\\_3.gif

-   CSNLW_D\_\$DATADATE\\\_3.gif

-   CSNSW_A\_\$DATADATE\\\_3.gif

-   CSNSW_B\_\$DATADATE\\\_3.gif

-   CSNSW_D\_\$DATADATE\\\_3.gif

-   CSN_B\_\$DATADATE\\\_3.gif

-   CSW_A\_\$DATADATE\\\_3.gif

-   CSW_B\_\$DATADATE\\\_3.gif

-   CSW_D\_\$DATADATE\\\_3.gif

-   CWN_A\_\$DATADATE\\\_3.gif

-   CWN_B\_\$DATADATE\\\_3.gif

-   CWN_D\_\$DATADATE\\\_3.gif

-   TALB_A\_\$DATADATE\\\_3.gif

-   TALB_B\_\$DATADATE\\\_3.gif

-   TALB_D\_\$DATADATE\\\_3.gif

-   TLW_A\_\$DATADATE\\\_3.gif

-   TLW_B\_\$DATADATE\\\_3.gif

-   TLW_D\_\$DATADATE\\\_3.gif

-   TNF_A\_\$DATADATE\\\_3.gif

-   TNF_B\_\$DATADATE\\\_3.gif

-   TNF_D\_\$DATADATE\\\_3.gif

-   TSDLW_B\_\$DATADATE\\\_3.gif

-   TSDSW_A\_\$DATADATE\\\_3.gif

-   TSDSW_B\_\$DATADATE\\\_3.gif

-   TSDSW_D\_\$DATADATE\\\_3.gif

-   TSDWN_A\_\$DATADATE\\\_3.gif

-   TSNLW_A\_\$DATADATE\\\_3.gif

-   TSNLW_B\_\$DATADATE\\\_3.gif

-   TSNLW_D\_\$DATADATE\\\_3.gif

-   TSNSW_A\_\$DATADATE\\\_3.gif

-   TSNSW_B\_\$DATADATE\\\_3.gif

-   TSNSW_D\_\$DATADATE\\\_3.gif

-   TSN_B\_\$DATADATE\\\_3.gif

-   TSW_A\_\$DATADATE\\\_3.gif

-   TSW_B\_\$DATADATE\\\_3.gif

-   TSW_D\_\$DATADATE\\\_3.gif

-   TWN_A\_\$DATADATE\\\_3.gif

-   TWN_B\_\$DATADATE\\\_3.gif

-   TWN_D\_\$DATADATE\\\_3.gif

#### Exit Codes

The processor CER10.1P1 terminates using the CERES-defined EXIT CODES
for the Langley TRMM Information System (LaTIS). Successful completion
is indicated by an exit code of 0. Failure is indicated by an exit code
202.

#### Main Processor Test Summary

Total Run Time: 15 minutes 47 seconds

Memory: 132752 K

Required Disk Space: 3.4 GB

### Evaluation Procedures

When running the production script, **CER10.1P1**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER10.1P1_LogReport\_\$INSTANCE, is
located in directory \$CERESHOME/tisa_avg/data/data_10/runlogs.

#### Metadata

Metadata files which end in extension,'.met', are located in the same
directory as their corresponding output files after CER10.1P1 has been
executed. Metadata files are written to directory,
\$CERESHOME/tisa_avg/data/data_10/out_comp.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_10/out_exp and new input files from the
execution are in \$CERESHOME/tisa_avg/data/data_10/out_comp. These input
files are accessed from those areas for the comparison.

**eval_ss10_output_Terra_FM2.csh** is a script needed to execute the
comparison program. Type the following:

> **cd \$CERESHOME/tisa_avg/test_suites/CER10.1P1**
>
> **eval_ss10_output_Terra_FM2.csh \$year \$month**
>
> **cmp \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_xglb\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_xglb\_\$INSTANCE**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script which removes
    PGE-created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To clean up the files for **Terra
    FM2** **CER10.1P1**:

> **\$CERESHOME/tisa_avg/bin/cleanup 10.1P1 \$year\$month**

## CER10.1P2 Main Processor

**[(NOTE: CER10.1P2 has to be run before running the test procedure for
CER 10.1P1 Terra.)]{.underline}**

### Stand Alone Test Procedures for Terra FM1

#### PCF Generator

The Main Processor production script, **CER10.1P2**, references a
Process Control File (PCF) which contain the correct file names and
paths for the test procedures. The PCF for the test case is created by
first executing an ASCII file generator,
**tisavg_10.1P2_ascii_ssit_gen.csh**, and then executing the PCF
generator, **tisavg_10.1P2_pcfgen.csh**.

For production runs, the ASCII file generator, tisavg_10.1P2_ascii_gen,
must be executed to create the ASCII input file for a particular
production run. The ASCII file generator requires 2 command line
arguments, 4-digit Data Year, 2-digit Data Month. The PCF generator,
tisavg_10.1P2_pcfgen.csh, is then executed using the newly created ASCII
input file name as a command line argument.

> **NOTE**: The PCF generator script, **tisavg_10.1P2_pcfgen.csh**, uses
> the file PCF.template. Therefore, PCF.template must exist in the same
> directory.

1.  Generate the ASCII input file for the test case:

**cd \$CERESHOME/tisa_avg/bin**

**source \$CERESENV**

**source \$CERESHOME/tisa_avg/bin/setup_test_env_Terra_FM1.csh**

**source \$CERESHOME/tisa_avg/bin/ENV10.1P2-env.csh**

**setenv year 2002**

**setenv month 07**

**setenv DATADATE 200207**

**setenv INSTANCE Terra-FM1-MODIS_SSIT_000000.\$DATADATE**

**\$CERESHOME/tisa_avg/bin/tisavg_10.1P2_ascii_ssit_gen.csh 10 \$year
\$month**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P2_PCFin\_\$INSTANCE

47. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P2_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER10.1P2_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P2_PCF\_\$INSTANCE

#### Execution

The production script is executed by typing the script name,
**CER10.1P2**, followed by one command-line argument: PCF file name.

> **\$CERESHOME/tisa_avg/bin/CER10.1P2 \$year \$month
> CER10.1P2_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER_10.1P2, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/ancillary/dynamic/**:

-   CER_SNOW-PCT\_\$INSTANCE

-   CER_SNOW-PCT\_\$INSTANCE.met

-   CER_mhr-csalb\_\$INSTANCE

-   CER_mhr-csalb\_\$INSTANCE.met

-   CER_csalb0-intrp2s\_\$INSTANCE

-   CER_csalb0-intrp2s\_\$INSTANCE.met

#### Exit Codes

All **CER10.1P2 software terminates using the CERES defined EXIT CODES**
for the Langley TRMM Information System (LaTIS). Successful completions
indicated by an exit code of 0.

#### Main Processor Test Summary

> Total Run Time: 2 minute and 33 seconds
>
> Memory: 55040 K
>
> Required Disk Space: 19.08 GB

### Evaluation Procedures

When running the production script, **CER10.1P2**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER10.1P2_LogReport\_\$INSTANCE is
located in directory \$CERESHOME/tisa_avg/data/data_10/runlogs.

#### Metadata

Metadata files which end in extension,'.met', are located in the same
directory as their corresponding output files after CER10.1P2 has been
executed.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_10/out_exp and new output files from the
execution are in \$CERESHOME/tisa_avg/data/ancillary/dynamic. These
output files are accessed from those areas for the comparison.

Since the output files are a binary and ascii files, the evaluation
software for CER10.1P2 does a diff on the one ascii file in out_exp and
the file created during processing and a cmp on the binary files:

> **cmp
> \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_SNOW-PCT\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_SNOW-PCT\_\$INSTANCE**

and

> **diff
> \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_mhr-csalb\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_mhr-csalb\_\$INSTANCE**

and

> **diff
> \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_csalb0-intrp2s\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_csalb0-intrp2s\_\$INSTANCE**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script which removes
    PGE-created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To clean up the files for **Terra
    FM1** **CER10.1P2**:

> **\$CERESHOME/tisa_avg/bin/cleanup 10.1P2 \$year\$month**

48. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

### Stand Alone Test Procedures for Terra FM2

**[(NOTE: CER10.1P2 has to be run before running the test procedure for
CER 10.1P1 Terra.)]{.underline}**

#### PCF Generator

The Main Processor production script, **CER10.1P2**, references a
Process Control File (PCF) which contain the correct file names and
paths for the test procedures. The PCF for the test case is created by
first executing an ASCII file generator,
**tisavg_10.1P2_ascii_ssit_gen.csh**, and then executing the PCF
generator, **tisavg_10.1P2_pcfgen.csh**.

For production runs, the ASCII file generator, tisavg_10.1P2_ascii_gen,
must be executed to create the ASCII input file for a particular
production run. The ASCII file generator requires 2 command line
arguments, 4-digit Data Year, 2-digit Data Month. The PCF generator,
tisavg_10.1P2_pcfgen.csh, is then executed using the newly created ASCII
input file name as a command line argument.

> **NOTE**: The PCF generator script, **tisavg_10.1P2_pcfgen.csh**, uses
> the file PCF.template. Therefore, PCF.template must exist in the same
> directory.

1.  Generate the ASCII input file for the test case:

**cd \$CERESHOME/tisa_avg/bin**

**source \$CERESENV**

**source \$CERESHOME/tisa_avg/bin/setup_test_env_Terra_FM2.csh**

**source \$CERESHOME/tisa_avg/bin/ENV10.1P2-env.csh**

**setenv year 2002**

**setenv month 07**

**setenv DATADATE 200207**

**setenv INSTANCE Terra-FM2-MODIS_SSIT_000000.\$DATADATE**

**\$CERESHOME/tisa_avg/bin/tisavg_10.1P2_ascii_ssit_gen.csh 10 \$year
\$month**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P2_PCFin\_\$INSTANCE

49. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P2_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER10.1P2_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P2_PCF\_\$INSTANCE

#### Execution

The production script is executed by typing the script name,
**CER10.1P2**, followed by one command-line argument: PCF file name.

> **\$CERESHOME/tisa_avg/bin/CER10.1P2 \$year \$month
> CER10.1P2_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER_10.1P2, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/ancillary/dynamic/**:

-   CER_SNOW-PCT\_\$INSTANCE

-   CER_SNOW-PCT\_\$INSTANCE.met

-   CER_mhr-csalb\_\$INSTANCE

-   CER_mhr-csalb\_\$INSTANCE.met

-   CER_csalb0-intrp2s\_\$INSTANCE

-   CER_csalb0-intrp2s\_\$INSTANCE.met

#### Exit Codes

All **CER10.1P2 software terminates using the CERES defined EXIT CODES**
for the Langley TRMM Information System (LaTIS). Successful completions
indicated by an exit code of 0.

#### Main Processor Test Summary

> Total Run Time: 2 minute and 33 seconds
>
> Memory: 55040 K
>
> Required Disk Space: 19.08 GB

### Evaluation Procedures

When running the production script, **CER10.1P2**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER10.1P2_LogReport\_\$INSTANCE is
located in directory \$CERESHOME/tisa_avg/data/data_10/runlogs.

#### Metadata

Metadata files which end in extension,'.met', are located in the same
directory as their corresponding output files after CER10.1P2 has been
executed.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_10/out_exp and new output files from the
execution are in \$CERESHOME/tisa_avg/data/ancillary/dynamic. These
output files are accessed from those areas for the comparison.

Since the output files are a binary and ascii files, the evaluation
software for CER10.1P2 does a diff on the one ascii file in out_exp and
the file created during processing and a cmp on the binary files:

> **cmp
> \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_SNOW-PCT\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_SNOW-PCT\_\$INSTANCE**

and

> **diff
> \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_mhr-csalb\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_mhr-csalb\_\$INSTANCE**

and

> **diff
> \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_csalb0-intrp2s\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_csalb0-intrp2s\_\$INSTANCE**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script which removes
    PGE-created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To clean up the files for **Terra
    FM2** **CER10.1P2**:

> **\$CERESHOME/tisa_avg/bin/cleanup 10.1P2 \$year\$month**

50. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

## CER10.1P3 Main Processor

### Stand-alone Test Procedures for Terra FM1

#### PCF Generator and Execution

The Main Processor production script, **CER10.1P3,** references a
Process Control File (PCF) which contains the correct file names and
paths for the test procedures. The PCF file for the test case is created
by first executing an ASCII file generator,
**tisavg_10.1P3_ascii_ssit_gen.csh**, and then executing the PCF
generator, **tisavg_10.1P3_pcfgen.csh**. The ASCII file generators
source Subsystem 10.0-specific environment script
**ENV10.1P3-env_ssit.csh** and **setup_test_env_Terra_FM1.csh**.

For production runs, the ASCII file generator,
**tisavg_10.1P3_ascii_ssit_gen.csh**, must be executed to create the
ASCII input file for a particular production run. The ASCII file
generator requires four command-line arguments: 2-digit subsystem
number(10); 4-digit Data Year(1998); 2-digit Data Month(02); and
1-character GGEO data file exist flag(Y), (optional, default value = Y).
The PCF generator, **tisavg_10.1P3_pcfgen.csh,** then must be executed
using the newly created ASCII input file name as a command-line
argument.

**NOTE:** The PCF generator script, **tisavg_10.1P3_pcfgen.csh**, uses
the file PCF.template. Therefore, PCF.template must exist in the same
directory.

1.  Generate the ASCII input file for the test case:

> **cd \$CERESHOME/tisa_avg/bin**
>
> **source \$CERESENV**
>
> **source \$CERESHOME/tisa_avg/bin/setup_test_env_Terra_FM1.csh**
>
> **source \$CERESHOME/tisa_avg/bin/ENV10.1P3-env_ssit.csh**
>
> **setenv year 2003**
>
> **setenv month 01**
>
> **setenv DATADATE 200301**
>
> **setenv INSTANCE Terra-FM1-MODIS_SSIT_000000.\$DATADATE**
>
> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P3_ascii_ssit_gen.csh 10 \$year
> \$month Y**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P3_PCFin\_\$INSTANCE

51. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P3_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER10.1P3_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P3_PCF\_\$INSTANCE

#### Execution

Execute the production script by typing the script name, **CER10.1P3**,
followed by three command-line arguments: year (YYYY), month (MM), and
PCF file name.

**\$CERESHOME/tisa_avg/bin/CER10.1P3 \$year \$month
CER10.1P3_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER10.1P3, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/data_10/out_comp**:

-   CER_SRBAVG-Daily1\_\$INSTANCE

-   CER_SRBAVG-Daily1\_\$INSTANCE.met

-   CER_SRBAVG-Daily2\_\$INSTANCE

-   CER_SRBAVG-Daily2\_\$INSTANCE.met

-   CER_SRBAVG-ISCCP-D2-like1\_\$INSTANCE

-   CER_SRBAVG-ISCCP-D2-like1\_\$INSTANCE.met

-   CER_SRBAVG-ISCCP-D2-like2\_\$INSTANCE

-   CER_SRBAVG-ISCCP-D2-like2\_\$INSTANCE.met

-   CER_QC-ISCCP-D2-NITE\_\$INSTANCE

-   CER_QC-ISCCP-D2-NITE\_\$INSTANCE.met

#### Exit Codes

The processor CER10.1P3 terminates using the CERES-defined EXIT CODES
for the Langley TRMM Information System (LaTIS). Successful completion
is indicated by an exit code of 0. Failure is indicated by an exit code
202.

#### Main Processor Test Summary

Total Run Time: 13 minutes 15 seconds

Memory: 190160K

Required Disk Space: 3.4 GB

### Evaluation Procedures

When running the production script, **CER10.1P3**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER10.1P3_LogReport\_\$INSTANCE, is
located in directory \$CERESHOME/tisa_avg/data/data_10/runlogs.

#### Metadata

Metadata files which end in extension,'.met', are located in the same
directory as their corresponding output files after CER10.1P3 has been
executed. Metadata files are written to directory,
\$CERESHOME/tisa_avg/data/data_10/out_comp.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_10/out_exp and new input files from the
execution are in \$CERESHOME/tisa_avg/data/data_10/out_comp. These input
files are accessed from those areas for the comparison.

**eval_ss10_output_Terra.csh** is a script needed to execute the
comparison program. Type the following:

> **cd \$CERESHOME/tisa_avg/test_suites/CER10.1P3**
>
> **eval_ss10_output_Terra_FM1.csh \$year \$month**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script which removes
    PGE-created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To clean up the files for **Terra
    FM1** **CER10.1P3**:

> **\$CERESHOME/tisa_avg/bin/cleanup 10.1P3 \$year\$month**

52. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

### Stand-alone Test Procedures for Terra FM2

#### PCF Generator and Execution

The Main Processor production script, **CER10.1P3,** references a
Process Control File (PCF) which contains the correct file names and
paths for the test procedures. The PCF file for the test case is created
by first executing an ASCII file generator,
**tisavg_10.1P3_ascii_ssit_gen.csh**, and then executing the PCF
generator, **tisavg_10.1P3_pcfgen.csh**. The ASCII file generators
source Subsystem 10.0-specific environment script
**ENV10.1P3-env_ssit.csh** and **setup_test_env_Terra_FM2.csh**.

For production runs, the ASCII file generator,
**tisavg_10.1P3_ascii_ssit_gen.csh**, must be executed to create the
ASCII input file for a particular production run. The ASCII file
generator requires four command-line arguments: 2-digit subsystem
number(10); 4-digit Data Year(1998); 2-digit Data Month(02); and
1-character GGEO data file exist flag(Y), (optional, default value = Y).
The PCF generator, **tisavg_10.1P3_pcfgen.csh,** then must be executed
using the newly created ASCII input file name as a command-line
argument.

**NOTE:** The PCF generator script, **tisavg_10.1P3_pcfgen.csh**, uses
the file PCF.template. Therefore, PCF.template must exist in the same
directory.

1.  Generate the ASCII input file for the test case:

> **cd \$CERESHOME/tisa_avg/bin**
>
> **source \$CERESENV**
>
> **source \$CERESHOME/tisa_avg/bin/setup_test_env_Terra_FM2.csh**
>
> **source \$CERESHOME/tisa_avg/bin/ENV10.1P3-env_ssit.csh**
>
> **setenv year 2003**
>
> **setenv month 01**
>
> **setenv DATADATE 200301**
>
> **setenv INSTANCE Terra-FM2-MODIS_SSIT_000000.\$DATADATE**
>
> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P3_ascii_ssit_gen.csh 10 \$year
> \$month Y**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P3_PCFin\_\$INSTANCE

53. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P3_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER10.1P3_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P3_PCF\_\$INSTANCE

#### Execution

Execute the production script by typing the script name, **CER10.1P3**,
followed by three command-line arguments: year (YYYY), month (MM), and
PCF file name.

**\$CERESHOME/tisa_avg/bin/CER10.1P3 \$year \$month
CER10.1P3_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER10.1P3, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/data_10/out_comp**:

-   CER_SRBAVG-Daily1\_\$INSTANCE

-   CER_SRBAVG-Daily1\_\$INSTANCE.met

-   CER_SRBAVG-Daily2\_\$INSTANCE

-   CER_SRBAVG-Daily2\_\$INSTANCE.met

-   CER_SRBAVG-ISCCP-D2-like1\_\$INSTANCE

-   CER_SRBAVG-ISCCP-D2-like1\_\$INSTANCE.met

-   CER_SRBAVG-ISCCP-D2-like2\_\$INSTANCE

-   CER_SRBAVG-ISCCP-D2-like2\_\$INSTANCE.met

-   CER_QC-ISCCP-D2-NITE\_\$INSTANCE

-   CER_QC-ISCCP-D2-NITE\_\$INSTANCE.met

#### Exit Codes

The processor **CER10.1P3 terminates using the CERES-defined EXIT
CODES** for the Langley TRMM Information System (LaTIS). Successful
completion is indicated by an exit code of 0. Failure is indicated by an
exit code 202.

#### Main Processor Test Summary

Total Run Time: 13 minutes 15 seconds

Memory: 190160 K

Required Disk Space: 3.4 GB

### Evaluation Procedures

When running the production script, **CER10.1P3**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER10.1P3_LogReport\_\$INSTANCE, is
located in directory \$CERESHOME/tisa_avg/data/data_10/runlogs.

#### Metadata

Metadata files which end in extension,'.met', are located in the same
directory as their corresponding output files after CER10.1P3 has been
executed. Metadata files are written to directory,
\$CERESHOME/tisa_avg/data/data_10/out_comp.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_10/out_exp and new input files from the
execution are in \$CERESHOME/tisa_avg/data/data_10/out_comp. These input
files are accessed from those areas for the comparison.

**eval_ss10_output_Terra_FM2.csh** is a script needed to execute the
comparison program. Type the following:

> **cd \$CERESHOME/tisa_avg/test_suites/CER10.1P3**
>
> **eval_ss10_output_Terra_FM2.csh \$year \$month**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script which removes
    PGE-created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To clean up the files for **Terra
    FM2** **CER10.1P3**:

> **\$CERESHOME/tisa_avg/bin/cleanup 10.1P3 \$year\$month**

54. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

### Stand-alone Test Procedures for Aqua FM3

#### PCF Generator and Execution

The Main Processor production script, **CER10.1P3,** references a
Process Control File (PCF) which contains the correct file names and
paths for the test procedures. The PCF file for the test case is created
by first executing an ASCII file generator,
**tisavg_10.1P3_ascii_gen-test.csh**, and then executing the PCF
generator, **tisavg_10.1P3_pcfgen.csh**. The ASCII file generators
source Subsystem 10.0-specific environment script
**ENV10.1P3-env_ssit.csh** and **setup_test_env_Aqua_FM3.csh**.

For production runs, the ASCII file generator,
**tisavg_10.1P3_ascii_gen.csh**, must be executed to create the ASCII
input file for a particular production run. The ASCII file generator
requires four command-line arguments: 2-digit subsystem number(10);
4-digit Data Year(1998); 2-digit Data Month(02); and 1-character GGEO
data file exist flag(Y), (optional, default value = Y). The PCF
generator, **tisavg_10.1P3_pcfgen.csh,** then must be executed using the
newly created ASCII input file name as a command-line argument.

**NOTE:** The PCF generator script, **tisavg_10.1P3_pcfgen.csh**, uses
the file PCF.template. Therefore, PCF.template must exist in the same
directory.

1.  Generate the ASCII input file for the test case:

> **cd \$CERESHOME/tisa_avg/bin**
>
> **source \$CERESENV**
>
> **source \$CERESHOME/tisa_avg/bin/setup_test_env_Aqua_FM3.csh**
>
> **source \$CERESHOME/tisa_avg/bin/ENV10.1P3-env_ssit.csh**
>
> **setenv year 2003**
>
> **setenv month 01**
>
> **setenv DATADATE 200301**
>
> **setenv INSTANCE Aqua-FM3-MODIS_SSIT_000000.\$DATADATE**
>
> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P3_ascii_ssit_gen.csh 10 \$year
> \$month Y**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P3_PCFin\_\$INSTANCE

55. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P3_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER10.1P3_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P3_PCF\_\$INSTANCE

#### Execution

Execute the production script by typing the script name, **CER10.1P3**,
followed by three command-line arguments: year (YYYY), month (MM), and
PCF file name.

**\$CERESHOME/tisa_avg/bin/CER10.1P3 \$year \$month
CER10.1P3_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER10.1P3, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/data_10/out_comp**:

-   CER_SRBAVG-Daily1\_\$INSTANCE

-   CER_SRBAVG-Daily1\_\$INSTANCE.met

-   CER_SRBAVG-Daily2\_\$INSTANCE

-   CER_SRBAVG-Daily2\_\$INSTANCE.met

-   CER_SRBAVG-ISCCP-D2-like1\_\$INSTANCE

-   CER_SRBAVG-ISCCP-D2-like1\_\$INSTANCE.met

-   CER_SRBAVG-ISCCP-D2-like2\_\$INSTANCE

-   CER_SRBAVG-ISCCP-D2-like2\_\$INSTANCE.met

-   CER_QC-ISCCP-D2-NITE\_\$INSTANCE

-   CER_QC-ISCCP-D2-NITE\_\$INSTANCE.met

#### Exit Codes

The processor CER10.1P3 terminates using the CERES-defined EXIT CODES
for the Langley TRMM Information System (LaTIS). Successful completion
is indicated by an exit code of 0. Failure is indicated by an exit code
202.

#### Main Processor Test Summary

Total Run Time: 13 minutes 15 seconds

Memory: 190160K

Required Disk Space: 3.4 GB

### Evaluation Procedures

When running the production script, **CER10.1P3**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER10.1P3_LogReport\_\$INSTANCE, is
located in directory \$CERESHOME/tisa_avg/data/data_10/runlogs.

#### Metadata

Metadata files which end in extension,'.met', are located in the same
directory as their corresponding output files after CER10.1P3 has been
executed. Metadata files are written to directory,
\$CERESHOME/tisa_avg/data/data_10/out_comp.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_10/out_exp and new input files from the
execution are in \$CERESHOME/tisa_avg/data/data_10/out_comp. These input
files are accessed from those areas for the comparison.

**eval_ss10_output_Aqua_FM3.csh** is a script needed to execute the
comparison program. Type the following:

> **cd \$CERESHOME/tisa_avg/test_suites/CER10.1P3**
>
> **eval_ss10_output_Aqua_FM3.csh \$year \$month**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script which removes
    PGE-created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To clean up the files for **Aqua FM3**
    **CER10.1P3**:

> **\$CERESHOME/tisa_avg/bin/cleanup 10.1P3 \$year\$month**

56. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

### Stand-alone Test Procedures for Aqua FM4

#### PCF Generator

The Main Processor production script, **CER10.1P3,** references a
Process Control File (PCF) which contains the correct file names and
paths for the test procedures. The PCF file for the test case is created
by first executing an ASCII file generator,
**tisavg_10.1P3_ascii_gen-test.csh**, and then executing the PCF
generator, **tisavg_10.1P3_pcfgen.csh**. The ASCII file generators
source Subsystem 10.0-specific environment script
**ENV10.1P3-env_ssit.csh** and **setup_test_env_Aqua_FM4.csh**.

For production runs, the ASCII file generator,
**tisavg_10.1P3_ascii_gen.csh**, must be executed to create the ASCII
input file for a particular production run. The ASCII file generator
requires four command-line arguments: 2-digit subsystem number(10);
4-digit Data Year(1998); 2-digit Data Month(02); and 1-character GGEO
data file exist flag(Y), (optional, default value = Y). The PCF
generator, **tisavg_10.1P3_pcfgen.csh,** then must be executed using the
newly created ASCII input file name as a command-line argument.

**NOTE:** The PCF generator script, **tisavg_10.1P3_pcfgen.csh**, uses
the file PCF.template. Therefore, PCF.template must exist in the same
directory.

1.  Generate the ASCII input file for the test case:

> **cd \$CERESHOME/tisa_avg/bin**
>
> **source \$CERESENV**
>
> **source \$CERESHOME/tisa_avg/bin/setup_test_env_Aqua_FM4.csh**
>
> **source \$CERESHOME/tisa_avg/bin/ENV10.1P3-env_ssit.csh**
>
> **setenv year 2003**
>
> **setenv month 01**
>
> **setenv DATADATE 200301**
>
> **setenv INSTANCE Aqua-FM4-MODIS_SSIT_000000.\$DATADATE**
>
> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P3_ascii_ssit_gen.csh 10 \$year
> \$month Y**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P3_PCFin\_\$INSTANCE

57. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P3_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER10.1P3_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P3_PCF\_\$INSTANCE

#### Execution

Execute the production script by typing the script name, **CER10.1P3**,
followed by three command-line arguments: year (YYYY), month (MM), and
PCF file name.

**\$CERESHOME/tisa_avg/bin/CER10.1P3 \$year \$month
CER10.1P3_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER10.1P3, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/data_10/out_comp**:

-   CER_SRBAVG-Daily1\_\$INSTANCE

-   CER_SRBAVG-Daily1\_\$INSTANCE.met

-   CER_SRBAVG-Daily2\_\$INSTANCE

-   CER_SRBAVG-Daily2\_\$INSTANCE.met

-   CER_SRBAVG-ISCCP-D2-like1\_\$INSTANCE

-   CER_SRBAVG-ISCCP-D2-like1\_\$INSTANCE.met

-   CER_SRBAVG-ISCCP-D2-like2\_\$INSTANCE

-   CER_SRBAVG-ISCCP-D2-like2\_\$INSTANCE.met

-   CER_QC-ISCCP-D2-NITE\_\$INSTANCE

-   CER_QC-ISCCP-D2-NITE\_\$INSTANCE.met

#### Exit Codes

The processor CER10.1P3 terminates using the CERES-defined EXIT CODES
for the Langley TRMM Information System (LaTIS). Successful completion
is indicated by an exit code of 0. Failure is indicated by an exit code
202.

#### Main Processor Test Summary

Total Run Time: 13 minutes 15 seconds

Memory: 190160 K

Required Disk Space: 3.4 GB

### Evaluation Procedures

When running the production script, **CER10.1P3**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER10.1P3_LogReport\_\$INSTANCE, is
located in directory \$CERESHOME/tisa_avg/data/data_10/runlogs.

#### Metadata

Metadata files which end in extension,'.met', are located in the same
directory as their corresponding output files after CER10.1P3 has been
executed. Metadata files are written to directory,
\$CERESHOME/tisa_avg/data/data_10/out_comp.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_10/out_exp and new input files from the
execution are in \$CERESHOME/tisa_avg/data/data_10/out_comp. These input
files are accessed from those areas for the comparison.

**eval_ss10_output_Aqua_FM4.csh** is a script needed to execute the
comparison program. Type the following:

> **cd \$CERESHOME/tisa_avg/test_suites/CER10.1P3**
>
> **eval_ss10_output_Aqua_FM4.csh \$year \$month**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script which removes
    PGE-created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To clean up the files for **Aqua FM4**
    **CER10.1P3**:

> **\$CERESHOME/tisa_avg/bin/cleanup 10.1P3 \$year\$month**

58. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

## CER10.1P4 Main Processor

### Stand-alone Test Procedures for Aqua FM3

**[(NOTE: CER10.1P5 has to be run before running this test procedure for
Aqua.)]{.underline}**

#### PCF Generator

The Main Processor production script, **CER10.1P4,** references a
Process Control File (PCF) which contains the correct file names and
paths for the test procedures. The PCF file for the test case is created
by first executing an ASCII file generator,
**tisavg_10.1P4_ascii_gen-test.csh**, and then executing the PCF
generator, **tisavg_10.1P4_pcfgen.csh**. The ASCII file generators
source Subsystem 10.0-specific environment script **ENV10.1P4_env.csh**
and **setup_test_env_Aqua_FM3.csh**.

For production runs, the ASCII file generator,
**tisavg_10.1P4_ascii_gen.csh**, must be executed to create the ASCII
input file for a particular production run. The ASCII file generator
requires four command-line arguments: 2-digit subsystem number(10);
4-digit Data Year(1998); 2-digit Data Month(02); and 1-character GGEO
data file exist flag(Y), (optional, default value = Y). The PCF
generator, **tisavg_10.1P4_pcfgen.csh,** then must be executed using the
newly created ASCII input file name as a command-line argument.

**NOTE:** The PCF generator script, **tisavg_10.1P4_pcfgen.csh**, uses
the file PCF.template. Therefore, PCF.template must exist in the same
directory.

1.  Generate the ASCII input file for the test case:

> **cd \$CERESHOME/tisa_avg/bin**
>
> **source \$CERESENV**
>
> **source \$CERESHOME/tisa_avg/bin/setup_test_env_Aqua_FM3.csh**
>
> **source \$CERESHOME/tisa_avg/bin/ENV10.1P4-env.csh**
>
> **setenv year 2002**
>
> **setenv month 07**
>
> **setenv DATADATE 200207**
>
> **setenv INSTANCE Aqua-FM3-MODIS_SSIT_999999.\$DATADATE**
>
> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P4_ascii_ssit_gen.csh 10 \$year
> \$month Y**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P4_PCFin\_\$INSTANCE

59. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P4_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER10.1P4_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P4_PCF\_\$INSTANCE

#### Execution

Execute the production script by typing the script name, **CER10.1P4**,
followed by three command-line arguments: year (YYYY), month (MM), and
PCF file name.

**\$CERESHOME/tisa_avg/bin/CER10.1P4 \$year \$month
CER10.1P4_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER10.1P4, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/data_10/out_comp**:

-   CER_SRBAVG1\_\$INSTANCE

-   CER_SRBAVG1\_\$INSTANCE.met

-   CER_SRBAVG2\_\$INSTANCE

-   CER_SRBAVG2\_\$INSTANCE.met

-   CER_SRBAVG3\_\$INSTANCE

-   CER_SRBAVG3\_\$INSTANCE.met

-   CER_NQCRP\_\$INSTANCE

-   CER_NQCRP\_\$INSTANCE.met

-   CER_NRGRP\_\$INSTANCE

-   CER_NRGRP\_\$INSTANCE.met

-   CER_NVREG\_\$INSTANCE

-   CER_NVREG\_\$INSTANCE.met

Create the following files in **\$CERESHOME/tisa_avg/web/tsplot:**

-   SURF_TSP\_\$DATADATE\\\_4.pdf

-   TOA_TSP\_\$DATADATE\\\_4.pdf

Create the following files in
**\$CERESHOME/tisa_avg/web/plot/gif/TAVG\_\$DATADATE\\\_4:**

-   CALB_A\_\$DATADATE\\\_4.gif

-   CALB_B\_\$DATADATE\\\_4.gif

-   CALB_D\_\$DATADATE\\\_4.gif

-   CLDO_HIGH\_\$DATADATE\\\_4.gif

-   CLDO_LMID\_\$DATADATE\\\_4.gif

-   CLDO_LOW\_\$DATADATE\\\_4.gif

-   CLDO_UMID\_\$DATADATE\\\_4.gif

-   CLDP_HIGH\_\$DATADATE\\\_4.gif

-   CLDP_LMID\_\$DATADATE\\\_4.gif

-   CLDP_LOW\_\$DATADATE\\\_4.gif

-   CLDP_UMID\_\$DATADATE\\\_4.gif

-   CLW_A\_\$DATADATE\\\_4.gif

-   CLW_B\_\$DATADATE\\\_4.gif

-   CLW_D\_\$DATADATE\\\_4.gif

-   CNF_A\_\$DATADATE\\\_4.gif

-   CNF_B\_\$DATADATE\\\_4.gif

-   CNF_D\_\$DATADATE\\\_4.gif

-   CSDLW_A\_\$DATADATE\\\_4.gif

-   CSDLW_B\_\$DATADATE\\\_4.gif

-   CSDLW_D\_\$DATADATE\\\_4.gif

-   CSDSW_A\_\$DATADATE\\\_4.gif

-   CSDSW_B\_\$DATADATE\\\_4.gif

-   CSDSW_D\_\$DATADATE\\\_4.gif

-   CSDWN_A\_\$DATADATE\\\_4.gif

-   CSNLW_A\_\$DATADATE\\\_4.gif

-   CSNLW_B\_\$DATADATE\\\_4.gif

-   CSNLW_D\_\$DATADATE\\\_4.gif

-   CSNSW_A\_\$DATADATE\\\_4.gif

-   CSNSW_B\_\$DATADATE\\\_4.gif

-   CSNSW_D\_\$DATADATE\\\_4.gif

-   CSN_B\_\$DATADATE\\\_4.gif

-   CSW_A\_\$DATADATE\\\_4.gif

-   CSW_B\_\$DATADATE\\\_4.gif

-   CSW_D\_\$DATADATE\\\_4.gif

-   CWN_A\_\$DATADATE\\\_4.gif

-   CWN_B\_\$DATADATE\\\_4.gif

-   CWN_D\_\$DATADATE\\\_4.gif

-   TALB_A\_\$DATADATE\\\_4.gif

-   TALB_B\_\$DATADATE\\\_4.gif

-   TALB_D\_\$DATADATE\\\_4.gif

-   TLW_A\_\$DATADATE\\\_4.gif

-   TLW_B\_\$DATADATE\\\_4.gif

-   TLW_D\_\$DATADATE\\\_4.gif

-   TNF_A\_\$DATADATE\\\_4.gif

-   TNF_B\_\$DATADATE\\\_4.gif

-   TNF_D\_\$DATADATE\\\_4.gif

-   TSDLW_B\_\$DATADATE\\\_4.gif

-   TSDSW_A\_\$DATADATE\\\_4.gif

-   TSDSW_B\_\$DATADATE\\\_4.gif

-   TSDSW_D\_\$DATADATE\\\_4.gif

-   TSDWN_A\_\$DATADATE\\\_4.gif

-   TSNLW_A\_\$DATADATE\\\_4.gif

-   TSNLW_B\_\$DATADATE\\\_4.gif

-   TSNLW_D\_\$DATADATE\\\_4.gif

-   TSNSW_A\_\$DATADATE\\\_4.gif

-   TSNSW_B\_\$DATADATE\\\_4.gif

-   TSNSW_D\_\$DATADATE\\\_4.gif

-   TSN_B\_\$DATADATE\\\_4.gif

-   TSW_A\_\$DATADATE\\\_4.gif

-   TSW_B\_\$DATADATE\\\_4.gif

-   TSW_D\_\$DATADATE\\\_4.gif

-   TWN_A\_\$DATADATE\\\_4.gif

-   TWN_B\_\$DATADATE\\\_4.gif

-   TWN_D\_\$DATADATE\\\_4.gif

#### Exit Codes

The processor CER10.1P4 terminates using the CERES-defined EXIT CODES
for the Langley TRMM Information System (LaTIS). Successful completion
is indicated by an exit code of 0. Failure is indicated by an exit code
202.

#### Main Processor Test Summary

Total Run Time: 26 minutes 13 seconds

Memory: 193520 K

Required Disk Space: 3.4 GB

### Evaluation Procedures

When running the production script, **CER10.1P4**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER10.1P4_LogReport\_\$INSTANCE, is
located in directory \$CERESHOME/tisa_avg/data/data_10/runlogs.

#### Metadata

Metadata files which end in extension,'.met', are located in the same
directory as their corresponding output files after CER10.1P4 has been
executed. Metadata files are written to directory,
\$CERESHOME/tisa_avg/data/data_10/out_comp.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_10/out_exp and new input files from the
execution are in \$CERESHOME/tisa_avg/data/data_10/out_comp. These input
files are accessed from those areas for the comparison.

**eval_ss10_output_Aqua_FM3.csh** is a script needed to execute the
comparison program. Type the following:

> **cd \$CERESHOME/tisa_avg/test_suites/CER10.1P4**
>
> **eval_ss10_output_Aqua_FM3.csh \$year \$month**
>
> **cmp \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_xglb\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_xglb\_\$INSTANCE**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script which removes
    PGE-created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To clean up the files for **Aqua FM3**
    **CER10.1P4**:

> **\$CERESHOME/tisa_avg/bin/cleanup 10.1P4 \$year\$month**

60. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

### Stand-alone Test Procedures for Aqua FM4

**[(NOTE: CER10.1P5 has to be run before running this test procedure for
Aqua.)]{.underline}**

#### PCF Generator

The Main Processor production script, **CER10.1P4,** references a
Process Control File (PCF) which contains the correct file names and
paths for the test procedures. The PCF file for the test case is created
by first executing an ASCII file generator,
**tisavg_10.1P4_ascii_gen-test.csh**, and then executing the PCF
generator, **tisavg_10.1P4_pcfgen.csh**. The ASCII file generators
source Subsystem 10.0-specific environment script **ENV10.1P4_env.csh**
and **setup_test_env_Aqua_FM4.csh**.

For production runs, the ASCII file generator,
**tisavg_10.1P4_ascii_gen.csh**, must be executed to create the ASCII
input file for a particular production run. The ASCII file generator
requires four command-line arguments: 2-digit subsystem number(10);
4-digit Data Year(1998); 2-digit Data Month(02); and 1-character GGEO
data file exist flag(Y), (optional, default value = Y). The PCF
generator, **tisavg_10.1P4_pcfgen.csh,** then must be executed using the
newly created ASCII input file name as a command-line argument.

**NOTE:** The PCF generator script, **tisavg_10.1P4_pcfgen.csh**, uses
the file PCF.template. Therefore, PCF.template must exist in the same
directory.

1.  Generate the ASCII input file for the test case:

> **cd \$CERESHOME/tisa_avg/bin**
>
> **source \$CERESENV**
>
> **source \$CERESHOME/tisa_avg/bin/setup_test_env_Aqua_FM4.csh**
>
> **source \$CERESHOME/tisa_avg/bin/ENV10.1P4-env.csh**
>
> **setenv year 2002**
>
> **setenv month 07**
>
> **setenv DATADATE 200207**
>
> **setenv INSTANCE Aqua-FM4-MODIS_SSIT_999999.\$DATADATE**
>
> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P4_ascii_ssit_gen.csh 10 \$year
> \$month Y**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P4_PCFin\_\$INSTANCE

61. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P4_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER10.1P4_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P4_PCF\_\$INSTANCE

#### Execution

Execute the production script by typing the script name, **CER10.1P4**,
followed by three command-line arguments: year (YYYY), month (MM), and
PCF file name.

**\$CERESHOME/tisa_avg/bin/CER10.1P4 \$year \$month
CER10.1P4_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER10.1P4, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/data_10/out_comp**:

-   CER_SRBAVG1\_\$INSTANCE

-   CER_SRBAVG1\_\$INSTANCE.met

-   CER_SRBAVG2\_\$INSTANCE

-   CER_SRBAVG2\_\$INSTANCE.met

-   CER_SRBAVG3\_\$INSTANCE

-   CER_SRBAVG3\_\$INSTANCE.met

-   CER_NQCRP\_\$INSTANCE

-   CER_NQCRP\_\$INSTANCE.met

-   CER_NRGRP\_\$INSTANCE

-   CER_NRGRP\_\$INSTANCE.met

-   CER_NVREG\_\$INSTANCE

-   CER_NVREG\_\$INSTANCE.met

Create the following files in **\$CERESHOME/tisa_avg/web/tsplot:**

-   SURF_TSP\_\$DATADATE\\\_5.pdf

-   TOA_TSP\_\$DATADATE\\\_5.pdf

Create the following files in
**\$CERESHOME/tisa_avg/web/plot/gif/TAVG\_\$DATADATE\\\_5:**

-   CALB_A\_\$DATADATE\\\_5.gif

-   CALB_B\_\$DATADATE\\\_5.gif

-   CALB_D\_\$DATADATE\\\_5.gif

-   CLDO_HIGH\_\$DATADATE\\\_5.gif

-   CLDO_LMID\_\$DATADATE\\\_5.gif

-   CLDO_LOW\_\$DATADATE\\\_5.gif

-   CLDO_UMID\_\$DATADATE\\\_5.gif

-   CLDP_HIGH\_\$DATADATE\\\_5.gif

-   CLDP_LMID\_\$DATADATE\\\_5.gif

-   CLDP_LOW\_\$DATADATE\\\_5.gif

-   CLDP_UMID\_\$DATADATE\\\_5.gif

-   CLW_A\_\$DATADATE\\\_5.gif

-   CLW_B\_\$DATADATE\\\_5.gif

-   CLW_D\_\$DATADATE\\\_5.gif

-   CNF_A\_\$DATADATE\\\_5.gif

-   CNF_B\_\$DATADATE\\\_5.gif

-   CNF_D\_\$DATADATE\\\_5.gif

-   CSDLW_A\_\$DATADATE\\\_5.gif

-   CSDLW_B\_\$DATADATE\\\_5.gif

-   CSDLW_D\_\$DATADATE\\\_5.gif

-   CSDSW_A\_\$DATADATE\\\_5.gif

-   CSDSW_B\_\$DATADATE\\\_5.gif

-   CSDSW_D\_\$DATADATE\\\_5.gif

-   CSDWN_A\_\$DATADATE\\\_5.gif

-   CSNLW_A\_\$DATADATE\\\_5.gif

-   CSNLW_B\_\$DATADATE\\\_5.gif

-   CSNLW_D\_\$DATADATE\\\_5.gif

-   CSNSW_A\_\$DATADATE\\\_5.gif

-   CSNSW_B\_\$DATADATE\\\_5.gif

-   CSNSW_D\_\$DATADATE\\\_5.gif

-   CSN_B\_\$DATADATE\\\_5.gif

-   CSW_A\_\$DATADATE\\\_5.gif

-   CSW_B\_\$DATADATE\\\_5.gif

-   CSW_D\_\$DATADATE\\\_5.gif

-   CWN_A\_\$DATADATE\\\_5.gif

-   CWN_B\_\$DATADATE\\\_5.gif

-   CWN_D\_\$DATADATE\\\_5.gif

-   TALB_A\_\$DATADATE\\\_5.gif

-   TALB_B\_\$DATADATE\\\_5.gif

-   TALB_D\_\$DATADATE\\\_5.gif

-   TLW_A\_\$DATADATE\\\_5.gif

-   TLW_B\_\$DATADATE\\\_5.gif

-   TLW_D\_\$DATADATE\\\_5.gif

-   TNF_A\_\$DATADATE\\\_5.gif

-   TNF_B\_\$DATADATE\\\_5.gif

-   TNF_D\_\$DATADATE\\\_5.gif

-   TSDLW_B\_\$DATADATE\\\_5.gif

-   TSDSW_A\_\$DATADATE\\\_5.gif

-   TSDSW_B\_\$DATADATE\\\_5.gif

-   TSDSW_D\_\$DATADATE\\\_5.gif

-   TSDWN_A\_\$DATADATE\\\_5.gif

-   TSNLW_A\_\$DATADATE\\\_5.gif

-   TSNLW_B\_\$DATADATE\\\_5.gif

-   TSNLW_D\_\$DATADATE\\\_5.gif

-   TSNSW_A\_\$DATADATE\\\_5.gif

-   TSNSW_B\_\$DATADATE\\\_5.gif

-   TSNSW_D\_\$DATADATE\\\_5.gif

-   TSN_B\_\$DATADATE\\\_5.gif

-   TSW_A\_\$DATADATE\\\_5.gif

-   TSW_B\_\$DATADATE\\\_5.gif

-   TSW_D\_\$DATADATE\\\_5.gif

-   TWN_A\_\$DATADATE\\\_5.gif

-   TWN_B\_\$DATADATE\\\_5.gif

-   TWN_D\_\$DATADATE\\\_5.gif

#### Exit Codes

The processor CER10.1P4 terminates using the CERES-defined EXIT CODES
for the Langley TRMM Information System (LaTIS). Successful completion
is indicated by an exit code of 0. Failure is indicated by an exit code
202.

#### Main Processor Test Summary

Total Run Time: 26 minutes 13 seconds

Memory: 193520 K

Required Disk Space: 3.4 GB

### Evaluation Procedures

When running the production script, **CER10.1P4**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER10.1P4_LogReport\_\$INSTANCE, is
located in directory \$CERESHOME/tisa_avg/data/data_10/runlogs.

#### Metadata

Metadata files which end in extension,'.met', are located in the same
directory as their corresponding output files after CER10.1P4 has been
executed. Metadata files are written to directory,
\$CERESHOME/tisa_avg/data/data_10/out_comp.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_10/out_exp and new input files from the
execution are in \$CERESHOME/tisa_avg/data/data_10/out_comp. These input
files are accessed from those areas for the comparison.

**eval_ss10_output_Aqua_FM4.csh** is a script needed to execute the
comparison program. Type the following:

> **cd \$CERESHOME/tisa_avg/test_suites/CER10.1P4**
>
> **eval_ss10_output_Aqua_FM4.csh \$year \$month**
>
> **cmp \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_xglb\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_xglb\_\$INSTANCE**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script which removes
    PGE-created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To clean up the files for **Aqua FM4**
    **CER10.1P4**:

> **\$CERESHOME/tisa_avg/bin/cleanup 10.1P4 \$year\$month**

62. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

## CER10.1P5 Main Processor

### Stand Alone Test Procedures for Aqua FM3

**[(NOTE: CER10.1P5 has to be run before running the test procedure for
CER10.1P4 Aqua.)]{.underline}**

#### PCF Generator

The Main Processor production script, **CER10.1P5**, references a
Process Control File (PCF) which contain the correct file names and
paths for the test procedures. The PCF for the test case is created by
first executing an ASCII file generator,
**tisavg_10.1P5_ascii_ssit_gen.csh**, and then executing the PCF
generator, **tisavg_10.1P5_pcfgen.csh**.

For production runs, the ASCII file generator, tisavg_10.1P5_ascii_gen,
must be executed to create the ASCII input file for a particular
production run. The ASCII file generator requires 2 command line
arguments, 4-digit Data Year, 2-digit Data Month. The PCF generator,
tisavg_10.1P5_pcfgen.csh, is then executed using the newly created ASCII
input file name as a command line argument.

> **NOTE**: The PCF generator script, **tisavg_10.1P5_pcfgen.csh**, uses
> the file PCF.template. Therefore, PCF.template must exist in the same
> directory.

1.  Generate the ASCII input file for the test case:

**cd \$CERESHOME/tisa_avg/bin**

**source \$CERESENV**

**source \$CERESHOME/tisa_avg/bin/setup_test_env_Aqua_FM3.csh**

**source \$CERESHOME/tisa_avg/bin/ENV10.1P5-env.csh**

**setenv year 2002**

**setenv month 07**

**setenv DATADATE 200207**

**setenv INSTANCE Aqua-FM3-MODIS_SSIT_000000.\$DATADATE**

**\$CERESHOME/tisa_avg/bin/tisavg_10.1P5_ascii_ssit_gen.csh 10 \$year
\$month**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P5_PCFin\_\$INSTANCE

63. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P5_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER10.1P5_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P5_PCF\_\$INSTANCE

#### Execution

The production script is executed by typing the script name,
**CER10.1P5**, followed by one command-line argument: PCF file name.

> **\$CERESHOME/tisa_avg/bin/CER10.1P5 \$year \$month
> CER10.1P5_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER10.1P5, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/ancillary/dynamic/**:

-   CER_SNOW-PCT\_\$INSTANCE

-   CER_SNOW-PCT\_\$INSTANCE.met

-   CER_mhr-csalb\_\$INSTANCE

-   CER_mhr-csalb\_\$INSTANCE.met

-   CER_csalb0-intrp2s\_\$INSTANCE

-   CER_csalb0-intrp2s\_\$INSTANCE.met

#### Exit Codes

All **CER10.1P5 software terminates using the CERES defined EXIT CODES**
for the Langley TRMM Information System (LaTIS). Successful completions
indicated by an exit code of 0.

#### Main Processor Test Summary

> Total Run Time: 2 minute and 33 seconds
>
> Memory: 55040 K
>
> Required Disk Space: 19.08 GB

### Evaluation Procedures

When running the production script, **CER10.1P5**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER10.1P5_LogReport\_\$INSTANCE is
located in directory \$CERESHOME/tisa_avg/data/data_10/runlogs.

#### Metadata

Metadata files which end in extension,'.met', are located in the same
directory as their corresponding output files after CER10.1P5 has been
executed.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_10/out_exp and new output files from the
execution are in \$CERESHOME/tisa_avg/data/ancillary/dynamic. These
output files are accessed from those areas for the comparison.

Since the output files are a binary and ascii files, the evaluation
software for CER10.1P5 does a diff on the one ascii file in out_exp and
the file created during processing and a cmp on the binary files:

> **cmp
> \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_SNOW-PCT\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_SNOW-PCT\_\$INSTANCE**

and

> **diff
> \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_mhr-csalb\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_mhr-csalb\_\$INSTANCE**

and

> **diff
> \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_csalb0-intrp2s\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_csalb0-intrp2s\_\$INSTANCE**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script which removes
    PGE-created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To clean up the files for **Aqua FM3**
    **CER10.1P5**:

> **\$CERESHOME/tisa_avg/bin/cleanup 10.1P5 \$year\$month**

64. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

### Stand Alone Test Procedures for Aqua FM4

**[(NOTE: CER10.1P5 has to be run before running the test procedure for
CER10.1P4 Aqua.)]{.underline}**

#### PCF Generator

The Main Processor production script, **CER10.1P5**, references a
Process Control File (PCF) which contain the correct file names and
paths for the test procedures. The PCF for the test case is created by
first executing an ASCII file generator,
**tisavg_10.1P5_ascii_ssit_gen.csh**, and then executing the PCF
generator, **tisavg_10.1P5_pcfgen.csh**.

For production runs, the ASCII file generator, tisavg_10.1P5_ascii_gen,
must be executed to create the ASCII input file for a particular
production run. The ASCII file generator requires 2 command line
arguments, 4-digit Data Year, 2-digit Data Month. The PCF generator,
tisavg_10.1P5_pcfgen.csh, is then executed using the newly created ASCII
input file name as a command line argument.

> **NOTE**: The PCF generator script, **tisavg_10.1P5_pcfgen.csh**, uses
> the file PCF.template. Therefore, PCF.template must exist in the same
> directory.

1.  Generate the ASCII input file for the test case:

**cd \$CERESHOME/tisa_avg/bin**

**source \$CERESENV**

**source \$CERESHOME/tisa_avg/bin/setup_test_env_Aqua_FM4.csh**

**source \$CERESHOME/tisa_avg/bin/ENV10.1P5-env.csh**

**setenv year 2002**

**setenv month 07**

**setenv DATADATE 200207**

**setenv INSTANCE Aqua-FM4-MODIS_SSIT_000000.\$DATADATE**

**\$CERESHOME/tisa_avg/bin/tisavg_10.1P5_ascii_ssit_gen.csh 10 \$year
\$month**

The following file will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P5_PCFin\_\$INSTANCE

65. Generate the PCF for the test case:

> **\$CERESHOME/tisa_avg/bin/tisavg_10.1P5_pcfgen.csh
> \$CERESHOME/tisa_avg/rcf/CER10.1P5_PCFin\_\$INSTANCE**

The following PCF will be generated in **\$CERESHOME/tisa_avg/rcf/**:

-   CER10.1P5_PCF\_\$INSTANCE

#### Execution

The production script is executed by typing the script name,
**CER10.1P5**, followed by one command-line argument: PCF file name.

> **\$CERESHOME/tisa_avg/bin/CER10.1P5 \$year \$month
> CER10.1P5_PCF\_\$INSTANCE**

The Main Processor, Product Generation Executive (PGE) CER10.1P5, will
be executed and will create the following files in
**\$CERESHOME/tisa_avg/data/ancillary/dynamic/**:

-   CER_SNOW-PCT\_\$INSTANCE

-   CER_SNOW-PCT\_\$INSTANCE.met

-   CER_mhr-csalb\_\$INSTANCE

-   CER_mhr-csalb\_\$INSTANCE.met

-   CER_csalb0-intrp2s\_\$INSTANCE

-   CER_csalb0-intrp2s\_\$INSTANCE.met

#### Exit Codes

All **CER10.1P5 software terminates using the CERES defined EXIT CODES**
for the Langley TRMM Information System (LaTIS). Successful completions
indicated by an exit code of 0.

#### Main Processor Test Summary

> Total Run Time: 2 minute and 33 seconds
>
> Memory: 55040 K
>
> Required Disk Space: 19.08 GB

### Evaluation Procedures

When running the production script, **CER10.1P5**, the system message,
'No match', may be written to the screen. This message occurs when the
script tries to remove an old output file that does not exist. This does
not signify a problem.

#### Log and Status File Results

The Error and Status Log File, CER10.1P5_LogReport\_\$INSTANCE is
located in directory \$CERESHOME/tisa_avg/data/data_10/runlogs.

#### Metadata

Metadata files which end in extension,'.met', are located in the same
directory as their corresponding output files after CER10.1P5 has been
executed.

#### Execution of Comparison Software

The delivered input files are in
\$CERESHOME/tisa_avg/data/data_10/out_exp and new output files from the
execution are in \$CERESHOME/tisa_avg/data/ancillary/dynamic. These
output files are accessed from those areas for the comparison.

Since the output files are a binary and ascii files, the evaluation
software for CER10.1P5 does a diff on the one ascii file in out_exp and
the file created during processing and a cmp on the binary files:

> **cmp
> \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_SNOW-PCT\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_SNOW-PCT\_\$INSTANCE**

and

> **diff
> \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_mhr-csalb\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_mhr-csalb\_\$INSTANCE**

and

> **diff
> \$CERESHOME/tisa_avg/data/data_10/out_exp/CER_csalb0-intrp2s\_\$INSTANCE
> \$CERESHOME/tisa_avg/data/ancillary/dynamic/CER_csalb0-intrp2s\_\$INSTANCE**

### Solutions to Possible Problems

1.  All output files are opened with status=NEW. These files must be
    removed before running test procedures. A script which removes
    PGE-created files, **cleanup**, is located in directory
    **\$CERESHOME/tisa_avg/bin**. To clean up the files for **Aqua FM4**
    **CER10.1P5**:

> **\$CERESHOME/tisa_avg/bin/cleanup 10.1P5 \$year\$month**

66. Environment variable F90 must be set to the 64-bit SGI F90 compiler.

#######  Acronyms and Abbreviations

ADM Angular Distribution Models

ASCII American Standard Code Information Interchange

ASDC Atmospheric Sciences Data Center

AVG Monthly Regional Radiative Fluxes and Clouds

CERES Clouds and the Earth's Radiant Energy System

CERESLib CERES Library

DAAC Distributed Active Archive Center

ECS EOSDIS Core System

EOS Earth Observing System

EOS-AM EOS Morning Crossing Mission

EOSDIS EOS Data Information System

EOS-PM EOS Afternoon Crossing Mission

ERBE Earth Radiation Budget Experiment

ERBS Earth Radiation Budget Satellite

FSW Gridded Single Satellite Fluxes and Clouds and Compute Spatial
Averages

GB Gigabytes

F90 Fortran 90

FOV Field-of-View

GGEO Geostationary data file

GMT Greenwich mean time

HDF Hierarchical Data Format

HDF-EOS Hierarchical Data Format - Earth Observing System

KB Kilobytes

LaRC Langley Research Center

LaTIS Langley TRMM Information System

LW Longwave

MB Megabytes

MCF Metadata Control Files

met metadata file

MM Two digit month

MOA Meteorological, Ozone, and Aerosol

N/A Not Applicable

NASA National Aeronautics and Space Administration

NOAA National Oceanic and Atmospheric Administration

PCF Process Control File

PGE Product Generation Executive

PMOA Post Meteorological, Ozone, and Aerosol

PSF Point Spread Function

QC Quality Control

SARB Surface and Atmospheric Radiation Budget

SDP Science Data Production

SFC Hourly Gridded Single Satellite TOA and Surface Fluxes and Clouds

SMF Status Message File

SRBAVG Monthly TOA and SRB Averages

SRD Software Requirements Document

SSAI Science Systems and Applications, Inc.

SW Shortwave

SYN Synoptic Radiative Fluxes and Clouds

TISA Time Interpolation and Spatial Averaging

TOA Top-of-the-Atmosphere

TRMM Tropical Rainfall Measuring Mission

TSI Time Space Interpolate

UT Universal Time

#######  Directory Structure Diagrams

[]{#__RefHeading___Toc188239716 .anchor}Figure B‑1. Directory Structure
for the TISA Averaging (tisa_avg) Tar File

Figure B-1. Directory Structure for the TISA Averaging (tisa_avg) Tar
File

Figure B-1. Directory Structure for the TISA Averaging (tisa_avg) Tar
File

#######  File Description Tables

######## Production Script

The following scripts must be moved to the production environment.

[]{#__RefHeading___Toc188179477 .anchor}Table C.1‑1. Production Scripts
@ (\$CERESHOME/tisa_avg/bin)

+------------------+----------+---------------------------------------+
| > File Name      | > Format | > Description                         |
+------------------+----------+---------------------------------------+
| > tisa           | > ASCII  | > C-Shell script which creates the    |
| vg_ascii_gen.csh |          | > PCF generator's ASCII file needed   |
|                  |          | > Main Processor PCF file generator   |
|                  |          | > script                              |
+------------------+----------+---------------------------------------+
| > tisavg_as      | > ASCII  | > C-Shell script which creates the    |
| cii_gen_test.csh |          | > PCF generator's ASCII file needed   |
|                  |          | > Main Processor PCF file generator   |
|                  |          | > script. **Not a production          |
|                  |          | > script.**                           |
+------------------+----------+---------------------------------------+
| > t              | > ASCII  | > C-Shell script which creates the    |
| isavg_pcfgen.csh |          | > PCF file for the main processor.    |
+------------------+----------+---------------------------------------+
| > setupenv.csh   | > ASCII  | > C-Shell script which sets the       |
|                  |          | > sampling strategy, production       |
|                  |          | > strategy, configuration code, SCCR  |
|                  |          | > environment variables.              |
+------------------+----------+---------------------------------------+
| > E              | > ASCII  | > C-Shell script which sets the       |
| NV10.1P1-env.csh |          | > sampling strategy and production    |
|                  |          | > strategy for SS10.                  |
+------------------+----------+---------------------------------------+
| > CER10.1P1      | > ASCII  | > C-Shell Script which executes the   |
|                  |          | > SS10 Main Processor                 |
+------------------+----------+---------------------------------------+

######## Executables

[]{#__RefHeading___Toc188179478 .anchor}Table C.2‑2. Executables

+--------------------+-----------+-------------------------------------+
| > File Name        | > Format  | > Description                       |
+--------------------+-----------+-------------------------------------+
| > tisa_710.exe^1^  | > Binary  | > Main Processor executable         |
+--------------------+-----------+-------------------------------------+
| > webplot.exe^1^   | > Binary  | > Executable to create data files   |
|                    |           | > for web plots                     |
+--------------------+-----------+-------------------------------------+
| > 1\. These files  |           |                                     |
| > will be          |           |                                     |
| > generated on     |           |                                     |
| > execution of     |           |                                     |
| > Subsystem        |           |                                     |
| > software and are |           |                                     |
| > not included in  |           |                                     |
| > the tar file.    |           |                                     |
+--------------------+-----------+-------------------------------------+

######## Status Message Files

[]{#__RefHeading___Toc188179479 .anchor}Table C.3‑3. Status Message
Files @ (\$CERESHOME/tisa_avg/smf)

+--------------------+-----------+-------------------------------------+
| > File Name        | > Format  | > Description                       |
+--------------------+-----------+-------------------------------------+
| > TISAVG_26300.t   | > ASCII   | > Status Message File for Subsystem |
|                    |           | > 10.0                              |
+--------------------+-----------+-------------------------------------+

######## Ancillary Input Data

[]{#__RefHeading___Toc188179480 .anchor}Table C.4‑4. Ancillary Input
Data @ (\$CERESHOME/tisa_avg/data/ancillary/static)

+-------------------------+---------+---------------------------------+
| > File Name             | >       | > Description                   |
|                         |  Format |                                 |
+-------------------------+---------+---------------------------------+
| > C                     | >       | > Directional Models, TOA       |
| ERES_DIR_MODEL.19971212 |  Binary |                                 |
+-------------------------+---------+---------------------------------+
| > Refl_Coef.19971107    | > ASCII | > Directional Models, Surface   |
+-------------------------+---------+---------------------------------+
| > NIISW03.19971101      | >       | > SW Angular Distribution       |
|                         |  Binary | > Models (ADM)                  |
+-------------------------+---------+---------------------------------+
| > NIILWAT.19971101      | >       | > LW ERBE ADM for Sep., Oct.,   |
|                         |  Binary | > Nov.                          |
+-------------------------+---------+---------------------------------+
| > NIILWSP.19971101      | >       | > LW ERBE ADM for Mar., Apr.,   |
|                         |  Binary | > May                           |
+-------------------------+---------+---------------------------------+
| > NIILWSM.19971101      | >       | > LW ERBE ADM for Jun., Jul.,   |
|                         |  Binary | > Aug.                          |
+-------------------------+---------+---------------------------------+
| > NIILWWN.19971101      | >       | > LW ERBE ADM for Dec., Jan.,   |
|                         |  Binary | > Feb                           |
+-------------------------+---------+---------------------------------+
| > georc.19971212        | >       | > Coefficient file.             |
|                         |  Binary |                                 |
+-------------------------+---------+---------------------------------+
| > CER_GGEO_CERES_       | >       | > GGEO product produced by      |
| Composite_007002.199801 |  Binary | > Subsystem 11.                 |
+-------------------------+---------+---------------------------------+
| > range_values.19980204 | > ASCII | > Contains valid range values   |
|                         |         | > for all TISA Averaging data   |
|                         |         | > product parameters            |
+-------------------------+---------+---------------------------------+
| >                       | > ASCII | > Contains the validation       |
|  valid_regions.19980316 |         | > region numbers.               |
+-------------------------+---------+---------------------------------+

######## Processing Control Files (PCF), Metadata Control Files (MCF)

[]{#__RefHeading___Toc188179481 .anchor}Table C.5‑5. Process Control
Files (PCF) @ (CERESHOME/tisa_avg/rcf)

+------------------------------+-----------+--------------------------+
| > File Name.                 | > Format  | > Description            |
+------------------------------+-----------+--------------------------+
| > CER                        | > ASCII   | > ASCII file created by  |
| 10.1P1_PCFin_TRMM-PFM-VIRS-V |           | > the ASCII file         |
| alidationR2_000000.199801^1^ |           | > generator to be used   |
|                              |           | > by the Main            |
|                              |           | > Processor's PCF        |
|                              |           | > generator              |
+------------------------------+-----------+--------------------------+
| > C                          | > ASCII   | > Process control file   |
| ER10.1P1_PCF_TRMM-PFM-VIRS-V |           | > for ss10 Main          |
| alidationR2_000000.199801^1^ |           | > Processor              |
+------------------------------+-----------+--------------------------+
| > 1\. These files will be    |           |                          |
| > generated on execution of  |           |                          |
| > Subsystem software and are |           |                          |
| > not included in the tar    |           |                          |
| > file.                      |           |                          |
+------------------------------+-----------+--------------------------+

[]{#__RefHeading___Toc188179482 .anchor}Table C.5‑6. Metadata Control
Files (MCF) for Subsystem 10.0 @ (\$CERESHOME/tisa_avg/rcf)

+-----------------+---------+------------------------------------------+
| > File Name     | >       | > Description                            |
|                 |  Format |                                          |
+-----------------+---------+------------------------------------------+
| > SRBAVGB.MCF   | > ASCII | > MCF for binary SRBAVG (SS10) Main      |
|                 |         | > Processor                              |
+-----------------+---------+------------------------------------------+
| > SRBAVG1.MCF   | > ASCII | > MCF for HDF-EOS SRBAVG1 (SS10) Main    |
|                 |         | > Processor                              |
+-----------------+---------+------------------------------------------+
| > SRBAVG2.MCF   | > ASCII | > MCF for HDF-EOS SRBAVG2 (SS10) Main    |
|                 |         | > Processor                              |
+-----------------+---------+------------------------------------------+
| > NQCRP.MCF     | > ASCII | > MCF for QC Report for SS10             |
+-----------------+---------+------------------------------------------+
| > NVREG.MCF     | > ASCII | > MCF for SS10 Validation File           |
+-----------------+---------+------------------------------------------+