Professional Documents
Culture Documents
Handbook TRMM PDF
Handbook TRMM PDF
11
10
H e i g h t ( k m)
9
8
7
6
5
4
3
2
1
0
0
50
100
150
Dis tan ce (km )
200
February 2001
Global environment change has become a worldwide concern in recent years. Satellite
remote sensing is recognized as a powerful and essential means for monitoring global
change of earth environment. The Tropical Rainfall Measuring Mission (TRMM) is a joint
mission between US and Japan, and it is the first satellite earth observation mission to
monitor tropical rainfall, which closely influences to global climate and environment
change.
TRMM was launched by the H-II rocket from NASDA/Tanegashima Space Center in
November 1997, and has gone into a circular orbit of altitude 350 km, inclination angle 35
and period 90 min. After launch, rainfall observation from TRMM was started, and the
designed routine operation period of 3 years was finished at the end of this January.
Currently, TRMM is continuing observation for enhanced scientific studies, and its
mission life is expected to extend for about 3 years.
TRMM observation data are received at the NASA ground station via Tracking and Data
Relay Satellite (TDRS), and some of observation data are transmitted from NASA Goddard
Space Flight Center (GSFC) to NASDA Earth Observation Center (EOC).
The purpose of this handbook is to provide users with necessary information for well and
spread utilization of TRMM data. We wish TRMM data with this handbook contribute your
studies on earth environment preservation, enhancement of climate change analysis, and so
on.
In closing, I would like to express my gratitude for assistance given by the PIs, CRL,
RESTEC and NASDA personnel who contributed their busy time.
February 2001
Earth Observation Center
National Space Development Agency of Japan
Purpose ................................................................................................................................1-1
Scope...................................................................................................................................1-1
TRMM Mission.....................................................................................................................1-1
Responsibilities of US and Japan...............................................................................................1-3
CONTENTS
ii
APPENDIX
Appendix-1ACRONYMS AND ABBREVIATIONS......................................... A1-1
Appendix-2RELATED INFORMATION ...................................................... A2-1
iii
CONTENTS
List of Figures
Figure 1.3-1
Figure 2.1-1
Figure 2.1-2
Figure 2.1-3
Figure 2.1-4
Figure 2.1-5
Figure 2.1-6
Figure 2.1-7
Figure 2.2-1
Figure 2.2-2
Figure 2.2-3
Figure 2.2-4
Figure 2.2-5
Figure 2.3-1
Figure 2.4-1
Figure 2.5-1
Figure 2.5-2
Figure 2.5-3
Figure 2.5-4
Figure 2.5-5
Figure 2.6-1
Figure 2.6-2
Figure 2.6-3
Figure 2.6-4
Figure 2.6-5
Figure 2.6-6
Figure 2.6-7
Figure 2.6-8
Figure 2.6-9
Figure 2.6-10
Figure 2.6-11
Figure 2.6-12
Figure 2.6-13
Figure 3.1-1
Figure 3.2-1
Figure 3.2-2
Figure 3.2-3
Figure 3.2-4
Figure 3.2-5
Figure 3.3-1
Figure 3.4-1
Figure 4.1-1
Figure 4.1-2
Figure 4.1-3
Figure 4.1-4
Figure 4.1-5
Figure 4.1-6
Figure 4.1-7
Figure 4.1-8
Figure 4.1-9
Figure 4.1-10
Figure 4.1-11
Figure 4.1-12
Figure 4.1-13
Figure 4.1-14
iv
Figure 4.1-15
Figure 4.1-16
Figure 4.1-17
Figure 4.2-1
Figure 4.2-2
Figure 4.2-3
Figure 4.2-4
Figure 4.2-5
Figure 4.2-6
Figure 4.2-7
Figure 4.2-8
Figure 4.2-9
Figure 4.2-10
Figure 4.2-11
Figure 4.2-12
Figure 4.2-13
Figure 4.2-14
Figure 4.2-15
Figure 4.2-16
Figure 4.2-17
Figure 4.2-18
Figure 4.2-19
Figure 4.2-20
Figure 4.4-1
Figure 5.1-1
Figure 5.3-1
Figure 5.3-2
Figure 5.4-1
Figure 5.4-2
Figure 5.4-3
Figure 5.4-4
Figure 5.4-5
Figure 5.4-6
Figure 6.1-1
Figure 6.2-1
Figure 6.2-2
Figure 6.2-3
Figure 6.3-1
Figure 6.3-2
Figure 6.3-3
Figure 6.4-1
Figure 6.4-2
Figure 6.4-3
Figure 6.4-4
Figure 6.4-5
Figure 6.4-6
CONTENTS
List of Tables
Table 1.4-1
Table 1.4-2
Table 2.1-1
Table 2.2-1
Table 2.2-2
Table 2.2-3
Table 2.2-4
Table 2.2-5
Table 2.2-6
Table 2.2-7
Table 2.2-8
Table 2.2-9
Table 2.2-10
Table 2.5-1
Table 2.5-2
Table 2.5-3
Table 2.6-1
Table 3.3-1
Table 3.3-2
Table 4-1
Table 4.1-1
Table 4.1-2
Table 4.1-3
Table 4.1-4
Table 4.1-5
Table 4.1-6
Table 4.1-7
Table 4.1-8
Table 4.1-9
Table 4.1-10
Table 4.2-1
Table 4.2-2
Table 4.2-3
Table 4.2-4
Table 4.3-1
Table 4.3-2
Table 5.2-1
Table 5.2-2
Table 5.2-3
Table 5.3-1
Table 5.3-2
Table 5.3-3
Table 5.3-4
Table 5.3-5
Table 6-1
vi
1 INTRODUCTION
TRMM, Tropical Rainfall Measuring Mission, was launched by the H-II rocket from Tanegashima
Space Center of NASDA, at AM 6:27 JST, November 28, 1997. This satellite has been developed
as a joint project between Japan and US, which is the first space mission dedicated to measuring
rain fall.
TRMM will mainly observe rain structure, rate and distribution in tropical and subtropical region,
the data is expected to play an important roll for understanding mechanisms of global climate
change and monitoring environmental variation.
1.1 Purpose
This handbook provides the necessary information to user to utilize TRMM data including
information related to standard products and also introduces reference information such as TRMM
spacecraft, onboard instruments, and ground systems.
1.2 Scope
This document consists of following 6 sections and appendices:
Section 1
: Describe the purpose and scope of the document and the overview of TRMM
mission;
Section 2 : Introduce the specifications of the TRMM satellite system and mission
instruments, the outline of TRMM orbit, and the TRMM operation policy;
Section 3 : Introduce the outline of the ground systems of NASDA and NASA;
Section 4 : Explain the outline of TRMM products provided by NASDA and HDF
format, and introduce various toolkits;
Section 5 : Present the outline of the TRMM products services to be provided by
NASDA/EOIS;
Section 6 : Explain TRMM mission status, results and future plan;
Appendices : Provide acronym list and reference information.
1-1
Section 1
INTRODUCTION
Among various components of the water budget, tropical rainfall, which comprises more than twothirds of global rainfall, is the primary driver of global atmospheric circulation as a hot source. The
knowledge of the tropical rainfall and its variability is therefore crucial to understand and to predict
the global climate system. In spite of its important role in our lives and global climate, the
measurement of global rainfall is extremely difficult because of its high spatial and temporal
variabilities. In particular, relatively few rainfall data has accumulated in the tropics and over
oceans.
Satellite remote sensing is probably the only way to provide reliable rainfall data in a global scale.
TRMM is the first space mission dedicated to measuring tropical and subtropical rainfall through
microwave and visible/infrared sensors, including the first spaceborne rain radar.
More than half the solar energy incident to the Earth is absorbed by the ocean and the land. This
absorbed energy causes the evaporation of the water from Earth surface. The water vapor
condensed aloft and then falls as rainfall. The latent heat release in this process is the major energy
source in the tropical atmosphere, and the driving force of global circulation.
Figure 1.3-1 shows examples of relationship between sea surface temperature and atmospheric
circulation in the tropics for the cases of normal and anomalous (El Nio) conditions. Warm water
distributed in the western pacific during the normal condition while warm water region shifted to
the east in the anomalous condition. Atmospheric circulation changes with the location of warm
water region.
The TRMM measurements are expected to provide a dataset that will be extremely valuable for
understanding and for predicting global climate change and weather anomalies such as related to
the sporadic "El Nio" phenomenon.
1-2
NASDA Japan
X
NASA US
X
X
X
X
X
X
X
Telemetry and science observation data of TRMM will be formatted in CCSDS packet basis, and
then transmitted to the White Sands station via TDRS. Pre-processing (Level 0 processing) of all
1-3
Section 1
INTRODUCTION
data and higher level processing of PR, TMI, and VIRS data will be conducted at GSFC. Level 0
processed CERES and LIS data will be transmitted to Langley Research Center and Marshall
Space Flight Center of NASA, respectively. PR Level 0 data will also be transmitted to Japan, and
its higher level processing will be performed at Earth Observation Center (EOC), NASDA. The
higher level products (Level 1-3 products) produced by EOC or GSFC will be distributed to users ,
which include many scientists in the field of climatology, meteorology, hydrology etc., in Japan,
US and various other countries.
NASDA Earth Observation Research Center (EORC) will promote scientific research using TRMM
data and provide researchers with scientific datasets.
Table 1.4-2 Responsibilities of Japan and US (related to data processing)
Primary Elements
Data Receiving
Preprocessing of All Data
Higher Level Processing of PR
Higher Level Processing of TMI
Higher Level Processing of VIRS
Higher Level Processing of CERES
Higher Level Processing of LIS
1-4
NASDA Japan
NASA US
X
X
X
X
X
X
X
2.1 Spacecraft
Table 2.1-1 shows the main characteristics of the TRMM satellite.
Table 2.1-1 Main Characteristics of the TRMM Satellite
Launch weight
Launcher
Launch date (JST)
Altitude
Inclination
Shape
The TRMM Observatory is comprised of a main body structure, eight housekeeping subsystems,
and five science instruments. This section provides a brief overview of the TRMM spacecraft
subsystems. The subsystems that comprise the TRMM spacecraft are as follows:
a.
b.
c.
d.
e.
f.
g.
h.
2-1
Section 2
Uplink card
Downlink card
Clock card
Spacecraft Processor
ACS Processor
2.2 Gbits of memory
Data storage of approximately 210 minutes will be provided by the C&DH subsystem in the form
of solid state recorders (Bulk Memory Cards). Figure 2.1-2 provides a block diagram of the
TRMM C&DH subsystem.
2-2
IDE B
LIGHT DATA SYS TEM (FDS)
IDE A
TTITUDE CONTROL
1773 BUS
C
CS PROCESSOR
T
o Side B
plink I/ F
VPC
LOCK
VPC
RANSPONDER
G
S
T
D
N
PLINK I/F
SPAC ECRAFT
1773 BUS
VPC
G
S
T
D
N
VPC
C
/C PROCESSOR
from FDS B
ownlink I/F
EMORY
.2 Gbit
OWNLINK
NTERFACE
-CHANNEL
-CHANNEL
STDN-CHANNEL
from FDS B
to FDS B
ownlink I/F
ownlink I/F
LVPC: Low Voltage Power Connector
S/C: Spacecraft
GS TDN: Ground Station
Figure 2.1-2
2-3
Section 2
Coarse Sun
Sensors (8)
Reaction Wheels (4)
igital Sun
ens ors (2)
M agnetic Torquer
Bars (3)
Inertial Reference
Unit (Three 2-Axes)
Engine Valve
Driver (A&B)
Flight Data System - B
Flight Data Sys tem - A
Three Axes
Magnetometers (2)
Earth Sensor
Ass embly
ACE-B
Attitude Control
Electronics-A
Solar Arrays
GSACE-B
imbal Solar
rray Contr ol
lectronics-A
High Gain
Antenna
Figure 2.1-3
2-4
POWER SUBSYSTEM
UNSWITCHED POWER
UNSWITCHED POWER
SWITCHED POWER
SWIT CHED POWER
SPSDU
SACE
PYROTECHNIC CONTROL
1773 BUS
UNSWITCHED POWER
SWITCHED POWER
DIS CR ETE COMMANDS
SERIAL COMMANDS
CLOCK DISTRIBUTION
IPSDU
2-5
Section 2
which provides the interface between the Power subsystem and the FDS. The PSIB also performs
power subsystem monitoring and control functions such as individual Battery Cell voltage
monitoring and Amp Hour Integration control of the SPRU. The SPRU provides peak power from
the solar array and charge control for the batteries using Voltage/Temperature and Constant Current
Control circuitry. The PBIU contains the battery and bus relays and directs power to the Essential
and Non-Essential busses. It also contains the battery and bus current shunts for monitoring
current flow through the system. Figure 2.1-5 shows a block diagram of the Power subsystem.
SE Electronics
ower System Interface Box (PSIB)
Standard Power
egulator Unit (SPRU)
Power Bus
nterface Unit
(PBIU)
Power
Module
olar
rray
atteri es
ssential Bus Powe r
ignal
2-6
OMNI
HCP
Directional
Couplers
DIPLEXER
RHCP
TRANSPONDER A
RF Combiner
HYBRID
ntennas
REC
TRANS
SW3
HYBRID
POWER AMPS
GA
BRF
BRF
CIR
RHCP
SW2
IR
SW4
APS
TRANSPONDER B
DIPLEXER
LHCP
Figure 2.1-6
SW1
TRANS
REC
2-7
Section 2
Pressurant Tank
Pressure Transducer (high)
Pyrotechnic Valve
Redundant Regulator
Tank 1
(forward)
Fill and
Drain
Module
Propellant
Tank
Module
Tank 2
(aft)
N2H4
Filters (2)
Tank Valve
-Pitch
+Pitch
-Yaw
+Yaw
-Roll
+Roll
-Roll
+Roll
Isolation
Valves (4)
-Yaw
+Yaw
-Pit ch
+Pitch
2.1.8 Deployables
The TRMM Deployables consists of a High Gain Antenna Deployment and Pointing System
(HGAD/PS), the Solar Array Deployment and Drive System (SADDS), and a Gimbal and Solar
Array Control Electronics (GSACE) box.
The High Gain Antenna (HGA) will be utilized for normal telemetry communications, provides a
2-axis Pointing System (PS) for tracking, and a High Gain Antenna Deployment System
(HGADS) to deploy and support the HGA and PS. The SADDS consists of two two-panel Solar
Array (SA) wings and two Solar Array Drive Assemblies (SADA). The GSACE controls the
position of both the HGA pointing system and the SA rotary actuators in the SADA.
2-8
When properly combined with TMI measurements, the PR data will be instrumental in obtaining
the height profile of the precipitation content, from which the profile of latent heat release from the
Earth can be estimated. The rain rate will be estimated from the radar reflectivity factor when the
rain rate is small by applying conventional algorithms used for ground-based radar. For large rain
rates, a rain attenuation correction will be made using the total-path attenuation of land or sea
surface echoes.
2.2.1.2 System Parameters
Figure 2.2-1 provides a graphical description of the PR instrument diagram. Table 2.2-1, Table
2.2-2 and Table 2.2-3 provide system parameters, Antenna subsystem parameters and
Transmitter/Receiver subsystem parameters respectively.
2-9
Section 2
Table 2.2-2
Antenna Type
Beam Width
Aperture
Scan Angle
Gain
Table 2.2-3
Transmitter Type
Peak Power
Pulse Width
Pulse Repetition Frequency (PRF)
Dynamic Range
2-10
2-11
Section 2
Table 2.2-4
Observation Frequency
Polarization
Horizontal Resolution
Swath Width
Scan Mode
Data Rate
Weight
Power
Table 2.2-5
Band
Center Freq.
(GHz)
Polarization
Width
(MHz)
Integral time
(s)
1
2
3
4
5
6
7
8
9
10.65
10.65
19.35
19.35
21.3
37.0
37.0
85.5
85.5
V
H
V
H
V
V
H
V
H
100
100
500
500
200
2000
2000
3000
3000
6.6
6.6
6.6
6.6
6.6
6.6
6.6
3.3
3.3
Table 2.2-6
1
2
3
4
5
6
7
Center Freq.
(GHz)
10.65
10.65
19.35
19.35
21.3
37.0
37.0
Polarization
V
H
V
H
V
V
H
Beam
efficiency (%)
93
93
96
96
98
91
92
Receiving
gain (K)
0.975
0.975
1.045
1.045
1.196
0.783
0.783
85.5
82
1.165
85.5
85
1.165
Band
Objective
Region
Ocean
Ocean
Ocean
Ocean
Ocean
Land/Ocean
Land/Ocean
Land
Ocean
Land
Ocean
passive microwave and radar observations are made. Data from the VIRS instrument will be used
in rain estimation algorithms based primarily on the passive and active microwave sensors.
The VIRS instrument possesses a radiative cooler, a Solar Calibrator door, an Earth Panel shield,
and a Solar Panel shield. The Earth panel shield will be deployed to block the Earth' s reflection,
and the Solar Panel shield will prevent the sun from shining into the VIRS .
Figure 2.2-3
2-13
Section 2
Optics
Spectroscopy
Focal Plane
Detector Cooling
Calibration
Data Rate
Weight
Power
Band 1
Clouds mapping
during daytime
0.63
0.10
100
10
Band 2
Identification between
water and ice
1.61
0.06
100
10
Band 3
Vapor
3.75
0.38
0.06K
5
Band 4
Temperature at
the top of clouds
10.80
1.00
0.06K
5
Band 5
Vapor
12.00
1.00
0.06K
5
2-14
Figure 2.2-4
Horizontal Resolution
Swath Width
Scan Mode
Data Rate
Weight
Power
Section 2
The LIS instrument will be powered ON during the initial instrument activation, and will remain
powered in that configuration for the duration of the mission (barring any unforeseen anomalous
conditions).
2-16
0.777655 m
4 km (nadir)
~ 600 km
Ave. 6 kbps
18 kg
42 W
2-1 7
Section 2
2-1 8
entry is carried out using the attitude control subsystem and the propulsion subsystem.
2-1 9
Section 2
Operation
(ACS)
Every Month
V Maneuver
Every 7 to 10 Days
Yaw Maneuver
2 to 4 Weeks
As required
As required
Definitive Orbit
ACS Performance Monitor
Command & Data Handling Recorder Playback
System (C&DH)
Recorder Retransmissions
Event Buffer Dump
Stored Command Processor Load
Flight S/W & Table Loads
Spacecraft Clock Maintenance
Power System
Communications System
2-2 0
Approximate Frequency
2-2 1
Section 2
conflict can not be resolved, the TRMM Joint Science Team and POD will come to an agreed upon
resolution. It should be noted that all required spacecraft maneuvers (180 yaw maneuver and
Delta-V maneuver) will take precedence over an instrument activity request. Given the following
activity priority guidelines, we believe that conflict resolution will not be necessary beyond the
SOCC/FOT interface.
The following list defines the priority of activities for the TRMM observatory.
1 . Any spacecraft anomaly (i.e. SafeHold, Low Power, etc.)
2 . Instrument Safing
3 . Recorder Playbacks
- TDRS events where recorder playbacks are scheduled (all TDRS events) will take precedence
over any event that would inhibit science data collection on the ground.
4. 180 yaw maneuver
5 . Delta-V maneuver
6 . Any rain instrument science activity, including anomaly troubleshooting for science
performance.
- This includes the PR Antenna Pattern Measurement (90 yaw)
7 . Any CERES or LIS instrument science activity, including anomaly troubleshooting for
science performance. - This includes the CERES Deep Space Calibration
The NASDA/EOC will have the primary responsibility for PR instrument planning. Planning aids
will be accessible to the EOC, via the SOCC, for PR instrument planning. All PR operation
requests will be checked by the EOC to verify that they will not be within PR operations
constraints before the activity time. The EOC will then send instrument activity requests and
information to the SOCC, for transfer to the FOT, for incorporation into the DAP. Basic conflict
resolution, if necessary, will be coordinated between the FOT and SOCC, with the EOC being
represented by the SOCC personnel.
For the scheduling of PR external calibrations, the NASDA/EOC will provide times corresponding
to when the TRMM spacecraft will pass over the Active Radar Calibrator (ARC). External
calibration commands will be placed into the daily command load, along with commands for an
internal calibration. Requests for the PR Antenna Pattern Measurement must be made by the PR
scientists at least 4 weeks in advance to allow for coordination with other observatory activities and
incorporation into the DAP. The FOT will coordinate the activity with all other instrument and
spacecraft activities. The time and beam angle necessary for the measurement will be provided by
the NASDA/EOC, via the SOCC. The necessary commands will be placed into the daily spacecraft
command load in order to perform the Antenna Pattern Measurement. During the planning process,
2-2 2
NASDA/EOC will receive verification of PR activities via the timeline report and, after load
generation, via the Integrated Print report. For planning of both the external calibration and the
antenna pattern measurements, NASDA/EOC will request 2 time windows. The second window
will only be scheduled as a backup in case of poor weather conditions during the first window
opportunity.
VIRS and TMI activities will be scheduled by the Instrument Scientists using the appropriate MOC
provided planning aids (Note: Planning aids will be distributed to the Instrument Scientists via the
SOCC). VIRS solar calibrations will be scheduled according to when the Sun is predicted to be in
the field of view of the VIRS solar calibration port.
The TMI instrument will not have any routine activity requests since TMI operates without
interruption throughout the mission. No nominal commands will be required. Any requested
activities for TMI will be incorporated only after an instrument activity request has been submitted.
Figure 2.5-2 shows the above mentioned instrument planning and scheduling operations and Table
2.5-2 shows the TRMM spacecraft maneuvers.
The TSDIS SOCC will assist with the planning and scheduling operations for the three rain
instruments (PR, TMI, VIRS). The FOT will provide planning and scheduling of CERES and LIS
activities, for the LaRC and MSFC instrument facilities. Observatory planning results in the
generation of a Daily Activity Plan (DAP). This plan contains the observatory commands required
for a single days operations. Once a DAP is generated and a confirmed TDRS schedule from the
NCC are in the MOC, constraint checking, modeling, and load generation for a given days
operations can begin.
Another major activity conducted in preparation for TRMM operations is SN contact scheduling.
This process begins approximately three weeks prior to the operational period when orbital data
products are received from the FDF. The FOTs interface with the NCC is via the User Planning
System (UPS), which provides automated schedule generation and electronic communications for
exchanging TDRS schedule requests and confirmed schedules.
2-2 3
Section 2
ime in Advance
OCC
weeks
OT
Operation
requests from
NASDA/EOC,
VIRS & TMI
Instrument
Scientists
weeks
imeline report
o remote users*
F
O
T
R, VIRS, TMI
Instrument
Activities
Spacecraft,
CERES, LIS
Activities
requiring S/C
reconfiguration
Inputs to
Mission
Planning
Timeline
peration
equests from
ngineers,
ERES & LIS
nstrument
cientists
spacecraft,
CERES, LIS
Activities
lanning Aids
DRS schedule
OT/SOCC
conflict
resolution
an't Resolve
week
-4 days
Resolved
OM/Joint
RMM Science
Team conflict
resolution
an't Resolve
riority
list
es
onflicts?
o Conflicts
esolved
OC
Generate
Activity
Plan
esolved
roblem
Perform
Load
Generation
Load Review
nd Approval
Transfer to
/T system
day
Figure 2.5-2
pproved
Uplink
Command
Load
Spacecraft Maneuvers
Activity
180 Yaw
(keep the Sun off the
+Y side of spacecraft)
Delta-V
(Orbit Attitude
Maintenance)
90 Yaw
(PR Antenna Pattern
Measurement)
Activity Duration
17 minutes
35 minutes
6 orbits
(non-contiguous
within 48 hours)
Settling Time
included in activity
duration
about 5 minutes
included in activity
duration
about 3 minutes
Frequency
every 2 to 4 weeks
PR Mode
VIRS Mode
TMI Mode
CERES Mode
LIS Mode
Normal
Normal
Normal
Contamination safe
Normal
2-2 4
2.5.2.1 PR
The PR instrument requires little day to day commanding. External calibrations will be performed
approximately every two months, and internal calibration once a week, respectively. Nominally,
the external calibration will be performed in the limited scan mode, which will use 7 of the 103
beams and disregard the remaining. The calibration must be performed when TRMM passes over
an ARC located in Japan. The NASDA/EOC will define the time and the center beam number at
which this calibration must be performed. An internal calibration will be performed in the area
where RF radiation of PR is prohibited.
The Antenna Pattern Measurement consists of two types of external calibrations; a cross track
antenna pattern and an along track antenna pattern. An Antenna Pattern Measurement will be
performed when an anomaly occurs on telemetry of SSPA or LNA, by using an ARC.
NASDA/EOC will provide times and a beam number to the FOT, via TSDIS SOCC. The Crosstrack Antenna Pattern Measurement will require a 90 yaw maneuver of the spacecraft to point the Y axis towards the velocity vector. The maneuver will take approximately 15 minutes (maneuver
and settling time). The calibration itself should only take approximately 5 minutes, at which time
the spacecraft will be yawed back to its nominal orientation ( X forward). Before the Cross-track
Antenna Pattern Measurement is initiated, the PR will be commanded to the external calibration,
fixed beam mode, in which a beam number is also commanded to the instrument. The beam
number will correspond to a specific angle which NASDA/EOC will use to point the ARC. The
Cross-track Antenna Pattern Measurement Calibration timeline is shown in Figure 2.5-3.
Table 2.5-3
PR Operational Modes
PR MODE
MODE DESCRIPTION
Observation This will be the normal operating mode of the instrument. During this mode, the PR instrument
performs normal rain echo measurements with a +17 scanning range.
External This mode will provide an on-orbit calibration of the PR instrument by the Active Radar
Calibration Calibrator(ARC) on the ground. Limited scan or Fixed beam submodes may be used in either the
spacecraft nominal configuration or the 90 yaw configuration.
Limited scan - scanning for 7 beam directions centered at a selected angle bin.
Fixed beam - Beam is fixed to a selected angle bin. No scanning is performed.
Internal This mode will provide an on-orbit calibration about the input-output charcteristics of LOGAMP
Calibration with internal loop signal. During this mode, no RF signal is radiated from the antenna and science
observation will not occur.
Health Check This mode is for checking RAMs and ROMs used in the System Control Data Processing (SCDP)
component. By electrical power turn-on, PR moves from Safety Mode to this mode.
LNA
This mode is used to check whether each LNA is alive or not. During this mode, no science
Analysis observation will occur.
Stand-By This mode is for checking the phase code stored in the SCDP. Also, this mode shall be selected to
temporarily stop the RF radiation. During this mode, the PR instrument is ON but is not initiating
any RF transmissions.
Safety
This mode will be used when the TRMM observatory is in either of the following modes of
operation:
- Launch Mode
- Initial Orbit Acquisition Mode
- Safe-Hold/Low Power Mode
When Safe-hold/Low Power signal is received, the PR instrument will be internally commanded to
this mode, prior to the autonomous removal of the NEB power supply. During this mode, the PR
instrument is OFF with the exception of the survival heaters.
2-2 5
Section 2
15 Min
5 Min
15 Min
90 Yaw
Calibration
90 Yaw
Normal Ops
2.5.2.2 TMI
The TMI instrument has a single operational mode and no commandable redundancy. Accordingly,
command procedures are minimal and will focus on power control. TMI essentially has two modes,
OFF and ON. After initial power-up, it is intended that the TMI will remain powered at all times,
barring any specific anomalies (i.e., Safehold, Low Power, TMI anomaly). In addition, no
commanding is intended for the remainder of the mission. General health and safety monitoring of
the TMI instrument during real-time events will be performed, and the SOCC will be notified of
any anomalous behavior.
2.5.2.3 VIRS
Commanding of the VIRS instrument will normally be minimal. Switching VIRS from the Day
mode to the Night mode will be accomplished by the spacecraft telemetry and statistics monitoring
(TSM) capability. The spacecraft processor will monitor for day/night conditions using the PSIB
"time of day" telemetry. The TSM will monitor for night conditions and then trigger an RTS. The
RTS will wait 3 minutes, command VIRS to Night mode, wait 20 minutes, then command VIRS
back to Day Mode. This will occur every orbit.
Solar calibrations will be performed approximately every 1-3 weeks, when the Sun is in the field
of view of the solar calibrator door. Planning aids will be utilized by the VIRS Instrument Scientist
to determine specific times of the calibration. Those times will be communicated via the SOCC to
the FOT for the inclusion of calibration commands into the daily spacecraft command load. Two
commands will be necessary for the VIRS solar calibration, a calibration door open and a
calibration door close command.
A 180 yaw maneuver will be performed every two to four weeks when the Sun reaches a Beta
angle of 0 in order to keep the Sun off the +Y side of spacecraft. The maneuver will be performed
in darkness (during eclipse) to avoid the possibility of the Sun shining on VIRS.
Normal operations for the VIRS instrument will consist of general health and safety monitoring of
instrument housekeeping data during real-time operations. Thermal monitoring of VIRS will also
be included. VIRS contains operational heaters which can provide 4 discrete amounts of heater
2-2 6
power to the VIRS scanner to maintain its temperature within a 0 to 20C range. The operational
heaters are commandable via the command link. Limits will be set and monitored on the ground
during real-time events. Figure 2.5-4 shows the operational temperature ranges.
50
40
30
Hot Limit
TC
/HO
EO L
Hot Limit
ITI O
D
CON
ASE
Restricted
Operational
Temperature
Range
20
10
0
-10
-20
-30
Cold Limi t
LD
/CO
EO L
E
CAS
D IT
CON
ION
10
15
Power Dissipated in Scanner, W
Cold Limit
20
2.5.2.4 CERES
CERES instrument commanding will be more frequent than any of the other instruments. The
majority of instrument commands will be issued from the spacecraft SCP (Stored Command
Processor). CERES instrument activities will be pre-approved by LaRC and then the activities will
be planned by the FOT.
During normal science operations, the instrument will operate in the Crosstrack and the Biaxial
Scan modes, 66% and 33% of the time, respectively. Operations in these two science gathering
modes will be interrupted periodically (every 2 weeks) to allow the instrument to perform solar and
internal calibrations. Internal calibrations are performed while the instrument is operating in either
the Crosstrack or Biaxial Scan modes while performing a normal Earth scan profile.
CERES will be placed into Crosstrack mode via stored command which will initiate execution of
an internal sequence. When in Crosstrack mode, the instrument will rotate only in elevation from
horizon to horizon, while being kept stationary at a fixed azimuth angle of 180.
While operating in the Biaxial scan mode, the azimuth gimbal will rotate back and forth (normally
between 90 and 270) while the elevation gimbal performs either a normal or short Earth scan
profile. Stored commands switch instrument operation between the normal and short Earth can
2-2 7
Section 2
profiles around sunrise and sunset to prevent the detectors from directly scanning the Sun. In
addition, a command will be sent prior to each normal scan command to trigger a count of the
scans during the normal scan profile. If the number of scans reaches the number specified as the
argument in the command, CERES will be autonomously commanded to the short scan profile.
The normal azimuth gimbal rotation range of 90 to 270 will be in effect when values of the beta
angle are less than -20 or greater than +20. When values of the beta angle are in the range
between -20 and +20, the azimuth gimbal will be restricted to rotate in a range between 110 and
250. The switch in instrument operation between the two azimuth rotation ranges is performed via
stored commands, whose times of execution are based on predicted values of beta angle. The
restricted azimuth rotation range (110 to 250) is necessary to prevent the detectors from scanning
closer than 20 to the Sun during sunrise and sunset.
CERES calibrations will be performed every two weeks. The elevation of the Sun during Solar
calibrations will be -11 and the azimuth of the instrument will be set to correspond with the
elevation angle so that the Sun is in the field of view of the MAM (Mirror Attenuator Mosaic).
Solar calibrations will be performed according to the preprogrammed sequence in the instruments
microprocessor. CERES will be commanded to Standby mode and then execute the calibration.
The sequence will last about 30 minutes and will return the instrument to the Standby mode upon
completion.
An internal calibration will normally be performed immediately after completion of a solar
calibration. The internal calibration sequence turns the internal calibration sources on and off in a
preprogrammed sequence. Calibration data are acquired while the elevation gimbal performs a
normal Earth scan profile and the instrument is operating in either the Crosstrack or Biaxial scan
mode.
A Deep Space Calibration will be performed during the instrument checkout period. To perform
this calibration, the CERES instrument will require that the TRMM spacecraft attitude be modified
from nadir pointing to an inertially fixed attitude.
The anomaly that an over voltage was loaded for the CERES instrument occurred around August
1998, 9 months after launch, analysis of the cause and some counterplans have been performed
until now. Therefore the science data acquisition is limited, intermittently done.
2-2 8
Figure 2.5-5
2.5.2.5 LIS
The operation of the LIS instrument is very basic. During normal science operations, the LIS
instrument will continuously operate, through day and night periods, in the science mode. The
instrument will acquire successive observations every 2 ms. If a lightning event is identified during
this 2 ms sample period, then the location, intensity, and time of each event is reported.
Once powered, the LIS instrument will be configured for a normal science data collection mode.
The FOT, during normal operations, need only to verify this configuration. In addition,
continuous automated limit checking will be performed during all real-time contacts with the
spacecraft. Instrument commanding will be somewhat frequent during L&EO until instrument
checkout has been completed. Operations will almost exclusively consist of changing the threshold
values in the RTEP (Real Time Event Processor). Once data is analyzed, and the best threshold
values are determined, commanding will be minimal. LIS does not have any requirements for
special configurations during spacecraft activities such as the Yaw maneuvers, Delta-V maneuvers,
or the CERES Deep Space Calibration.
2-2 9
Section 2
Abbreviation Quantity
Remarks
ANT
1 set 128 waveguide slot antennas
SSPA
128
Divided into 17 types at the output
LNA
128 Divided into 17 types at the gain
DIV/COMB1
1
16 divided/combined waves
DIV/COMB2
16
8 divided/combined waves including the
phase shifter
Transmit drive amplifier
TDA
2
Redundant configuration
Receive drive amplifier
RDA
2
Redundant configuration
Band-pass filter
BPF
2
Redundant configuration
Same as the one used in FCIF.
RF power supply
RF PS
2
Redundant configuration
System control/data
SCDP
2
Redundant configuration
Signal processing processing assembly
subsystem (SP) Frequency converter/IF
FCIF
2
Redundant configuration
assembly
PLO unit
PLO
1
Internal redundant configuration. Power
is supplied from FCIF.
Structure subsystem
STR
1 set
Thermal control subsystem
TCS
1 set
Integration subsystem
INT
1 set
2-3 0
(2) Appearance
The appearance of the precipitation radar is shown in Figure 2.6-1.
(3) Function Block Diagram
The functional block diagram of the precipitation radar is shown in Figure 2.6-2.
2-3 1
Section 2
Figure 2.6-2
2-3 2
2.6.2 Functions
The major functions of the precipitation radar are as follows:
(1) Major Functions
The major functions of the precipitation radar are as follows. Measurement conceptual diagram is
shown in Figure 2.6-3.
1) Transmits short sinusoidal waves in the direction of the earth, and receives the radar echo
scattered by raindrops and the like from a range necessary to find out the vertical distribution
of rainfall.
2) A beam is scanned within a plane that is vertical to the direction in which TRMM observatory
is traveling so as to find out the three-dimensional structure of rainfall.
3) Averages the total of 64 pulses received in 32 pulse lots from two frequencies.(Two
frequency agility.)
4) Measures quantitatively the radar received power, the radar reflectivity factor (Z factor), and
the normalized scattering cross section of earth surface (0 ) (internal calibration function,
5)
6)
7)
8)
2-3 3
Section 2
TRMM Observatory
H: Satellite Altitude 350 km
Flight Direction
Bright Band
Rmin H - 20 km
Rmax H/cos m
0.5 km
Range Resolution 250 m
Rain Area 5 km
following two submodes depending on the scan method of the antenna beam.
Limited Scan Mode : A mode where 7 beams (0.355 intervals) centering a round the specified
observation angle bin are scanned. This mode is a specific mode so that it can certainly receive
a reference signal by closer pitch scan than the observation mode.
Fixed Beam Mode : A mode fixed to a specified scan angle bin. (No scanning.)
2-3 5
Section 2
External Cal
(Limited scan)
Internal calibration
Observation
External
Calibration
(fixed Beam)
Standby
Analysis
Health Check
Safty
Transition by command
Transition by command or signal from spacecraft
Transition by power source from spacecraft command
State of RF Emission
State of non RF Emission
Figure 2.6-4
2.6.3 Performance
The main performances of the precipitation radar are as follows:
2-3 6
1) Frequency
2) Transmission
frequency stability
3) Occupied bandwidth
4) Spurious
5) Range resolution
6) Horizontal resolution
: within 14 MHz
: 50 dBc or less (at antenna subsystem input/output port)
: 250 m or less (normal at 6 dB width of reception filter output pulse)
: 4.34 0.12 km or less at nadir with a physical altitude of 350 km.
(Horizontal resolution on the ground where the normal is 6 dB width
of the transmit/receive round-trip antenna pattern.)
7) Minimum radar echo : -111 dBm
Reception level (Smin) (The value at the interface point with the
antenna subsystem. It is a reception level where S/N for each pulse
becomes 0 dB. Antenna input noise temperature is assumed to be
290 K.)
8) Minimum measurable : 0.5 mm/h (S/N per pulse = 0 dB at the peak of rain area.)
rainfall intensity
9) Scan width
a. During observation : 215 km or more (Between centers of the width footprint at the
mode
surface when geographical altitude is at 350 km.)
10) Scan angle interval and the number of scan angle bins within each scan
a. During observation : Scan angle interval : 2 scan angle bins (about 0.71 degree)
mode
Number of scan angle bins : 49 (including nadir)
11) Scan cycle
a. During observation : 0.6 seconds or less
mode
12) Antenna orientation fix : During the external calibration mode, it is possible to fix the antenna
beam direction at the scan angle specified within the scan angle bins,
in addition to antenna scan provided in 9) to 11).
13) Observation range
a. During observation : It is possible to observe surface echo by antenna main lobes from
an altitude of 20 km1 . Furthermore, at a scan angle of 0, a mirror
image of up to an altitude of 5 km is included.
14) System noise level
: Measured within the range at which the radar echo can be ignored.
15) Averaged individual sample number of a radar video signal : 64 or more
16) Dynamic range
: Because both the surface echo level and the noise level are measured
simultaneously at nadir (0 at sea surface shall be 16 dB, and the
antenna input noise temperature shall be 120 K), the linear section of
the receiver integrated input/output characteristic (a characteristic
where receive subsystem noise is assumed to be ignorable and
includes logarithm detector, and A/D conversion) to the sinusoidal
pulse input has a margin of 5 dB or more above and below the noise
and surface echo levels provided in this section.
17) Linearity
: Within 0.6 dB in the linear section of 16).
18) Range reference point2 determination precision: 10 % or less of range resolution
19) Measurement precision
a. Equivalence Z-factor and surface normalized radar cross section: within 1 dB3, 4
b. Radar receive power : within 0.9 dB4
c. Radar transmit power: within 0.4 dB
It measures range up to 23 km originally, but only the data by 20 km will be used finally.
It is an assumed point where the distance from the precipitation radar is taken to be 0; and it shall be range bin 1.
3
Excludes error caused by rainfall and atmosphere attenuation.
4
Excludes error caused by statistical variation for each pulse in the radar reception level. This provision is applied to
the signal level within the dynamic range provided in 16).
2
2-3 7
Section 2
20) Surface echo strength : Less or equal to 0.5 mm/h rainfall echo strength within the
by the antenna side
observation range provided in 13). Antenna side lobes shall be
lobes and the cross
-20 dB or less than the noise level, and cross polarization grating
polarization grating
lobes shall be -5 dB or less than the noise level in the system noise
lobes
detection window provided in 14). Antenna input noise temperature
shall be 120 K .
21) Range side lobes for receive pulse: -25 dB or less
22) Reception filter loss : 1.5 dB or less
23) Antenna gain
: 47.4 dB or more (At antenna subsystem input/output port)
24) Antenna beam half: 0.71 0.02 degrees (at nadir)
width
0.74 0.03 degrees (at a scan angle of 17 degrees)
25) Antenna side lobes
: peak value -27 dB or less
integration value at the same range -64 dB or less (040)
26) Inclination angle of antenna beam: 4 0.1 degrees to the direction of feeding point
27) Maximum antenna scan angle
: 17 degrees or more in the cross track direction
28) Grating lobes
: Not generated when the antenna is scanned within the scan angle
range provided in 27).
29) Cross polarization grating lobes: -15 dB
30) Transmit/receive beam orientation conformity: within 0.07
31) Beam orientation precision : The error of the antenna beam orientation (uncertainty) to
the radar alignment reference is within 0.2.
32) Range bin
a. Number of range bins : 400
b. Range bin intervals
: 125 m 1 m
33) Scan angle bin
a. Number of scan angle : 103
b. Scan angle bin intervals: 0.355 0.1
(radar echo) where transmitted pulse waves return after being scattered by raindrops and the
ground surface. For each transmitted pulse, received power of the radar echo to an altitude of 20
km from the ground surface are sampled approximately every 250 m in terms of a range in the
beam direction. Sixty four (32 pulses x 2 frequencies) received power sampling data for the same
distance (same range) in a beam direction are averaged and transmitted to the ground. Sixty four
data made up from 32 pulses of two frequencies is statistically independent sample data, and taking
their average ensures the necessary observation precision (S/N). The method of using two
transmission frequencies to ensure independent sample numbers is called 2 frequency agility
method. The precipitation radar scans once every 0.6 seconds in the direction which is
perpendicular (cross track direction) to the direction in which the satellite is travelling (along track
direction). There are 49 beams (observation angle bins) with a beam every 0.71 degrees within the
range of 17 degrees with the center at nadir. Each scan carries out observation to 49 beam
directions. The precipitation radar on board the TRMM is an active phased array system radar
where a transmitter and a receiver are connected to the 128 waveguide slotted antenna. It carries
out beam scan by controlling the phase of 128 system active array using a digital phaser so that
they correspond to each beam direction. The antenna pattern of the precipitation radar realizes an
extremely low side lobe level through a power supply conforming to the Taylor distribution in both
the along track direction and the cross track direction so as not to influence the observation
precision that is caused by the strong ground surface echo, which comes in from the side lobe
direction of the antenna, superimposing with the precipitation echo that is observed by the main
beam at the same range. Power supply distribution in the along track direction is realized by the
way slots are cut in each of the waveguide slot antennas, and the power supply distribution in the
cross track direction is realized by the transmission power distribution of the 128 transmitters. The
precipitation radar is designed so that observation data can be obtained correctly within the satellite
altitude range 350 km + 7 km and - 8 km. Outside this altitude range, a part of the received echo
data may go missing, or ground surface echo may not be included in the observation data.
Observation of precipitation using a radar from space differs from precipitation radar on the ground
in that its radar echo contains a strong scattering echo from the ground surface or the sea surface.
The rainfall attenuation from this strong echo can be used to improve the accuracy of the estimated
rainfall intensity. The observation data of this precipitation radar is sampled for each range
resolution (250 m) determined by the radar pulse width. However, ground surface echo near the
vertical incidence is extremely strong, and hence it is difficult to seek accurate echo levels for each
250 m sample. Therefore to reduce the observation error, data is obtained at 125 m sample
intervals. This is called over sample, and it tracks ground surface echo and obtains data near that
region in a minute detail. These processings are carried out by the data processing algorithm
installed in the system control/data processing assembly of this precipitation radar.
2-3 9
Section 2
Components
Antenna subsystem
TransmitReceive
subsystem (TRS)
Power amplifier
Low noise amplifier
Divider / Combiner1
Divider / Combiner2
Transmit drive amplifier
Receive drive amplifier
Band-pass filter
RF power supply
Signal
proceprocessing
subsystem (SP)
Structual subsystem
Thermal control subsystem
Integration subsystem
transmit-receive subsystem, it scans the antenna beam orientation within a plane that is
perpendicular to the direction in which the TRMM observatory is travelling.
(3)
1)
2)
3)
4)
5)
6)
7)
8)
9)
10)
11)
12)
13)
14)
15)
Performance
Antenna formation
: Non-resonating waveguide slot array antenna
Number of antenna elements
: 128
Electric aperture diameter : 2.1 m x 2.1 m
Center frequency
: 13.796 GHz (f1) and 13.802 GHz (f2) (2 cycle frequency agility)
Polarized wave
: Horizontally polarized wave
Bandwidth
: 10 MHz or more
Efficiency
: 95 % or more
Waveguide loss
: 0.5 dB or less
VSWR
: 1.2 or less (Antenna element unit characteristic)
Gain
: 47.4 dB or more (At antenna subsystem input/output port)
Beam half-width
: 0.71 0.02 degrees (nadir)
0.74 0.03 degrees (at scan angle of 17 degrees)
Side lobes
: Peak value -27 dB or less
Beam inclination angle : 4 0.1 degrees to feeding point
Maximum scan angle : 17 degrees or more in the cross track direction
Coordinate axes of the antenna subsystem: Mechanical coordinate axis (Xa, Ya, Za), and
electric coordinate axis (Xe, Ye, Ze) are used for the coordinate axes
of the antenna subsystem. These coordinate axes are shown in
Figure 2.6-6.
Precipitation radar/antenna subsystem
electric coordinate axis
Antenna subsystem
mechanical coordinate axis
Ze
Za
Ye
Xe
4 degrees
Antenna subsystem
Xa
Zm
Xm
Ym
Precipitation radar mechanical
coordinate axis
2-4 1
Section 2
2-4 2
(b) Function
1) Possesses a gain satisfying the conditions of reception antenna pattern.
2) Possesses a T/R switch used to protect LNA and to prevent effects on other circuits caused by
transmit pulse leakage during transmission.
3) Carries out T/R switch control by control signals.
(3) Divider/Combiner 1
(a) Function
1) During transmission, it inputs the RF transmission pulses supplied from the frequency
converter/IF assembly of the signal processing subsystem, and outputs them to the
divider/combiner 2 after branching them into 16.
2) During reception, it inputs the RF signals from the 16 system divider/combiner 2, and output
them to the frequency converter/IF assembly after combining them.
3) Possesses a circulator used to isolate the input/output signals to the frequency converter/IF
assembly, as well as a signal dividing/combining hybrid.
4) To correspond to the two frequency converter/IF assemblys which include the redundant
systems, it is provided with two input/output terminals into the frequency converter/IF
assemblys for both transmission and reception.
(4) Divider/Combiner 2
(a) Structure
Divider/combiner 2 (DIV/COMB2) is made up of hybrid (HYB), 5 bit digital phase shifter (PHS),
and isolator (ISO)/circulator (CIR).
(b) Function
1) During transmission, it inputs the RF transmission pulse from divider/combiner 1, then
branches it into 8 signals and outputs them to SSPA after adjusting them to required phases
using a digital phase shifter.
2) During reception, it inputs the RF signals from 8 system LNAs, adjusts them to required
phase volume and outputs them to divider/combiner 1 after combining them.
3) Possesses a circulator in SSPA/LNA output side which is used for isolating the input/output
signals.
4) Enables control of the digital phase shifter using control signals.
(5) Power Supply
(a) Structure
Power supply (RF system) is made up of the primary and the redundant system, and are mutually
connected by wired OR in precipitation radar system harness. Because it is the power supply for
2-4 3
Section 2
2-4 4
4)
5)
6)
7)
8)
9)
Function
Generates 2 frequency pulses, and supplies the transmit-receive subsystem.
Stops generation of either or both of the 2 frequency pulses by a command.
Carries out frequency conversion, IF amplification, band limiting, and logarithmic wave
detection of the radar transmission/reception signals output from the transmit-receive
subsystem, and output radar video signals to the system control/data processing section.
Possesses RF signal reflection loop so as to enable calibration of the receive input/output
characteristic on the ground. Also, calibration is controlled by the control signals.
(This function is used with the internal calibration mode of the precipitation radar system.)
To monitor the output video voltage drift, it carries out matched termination at the input port of
the logarithm wave detector by control signals.
Adjusts the reception gain by a command. (Varies to 5 steps in 3 dB step.)
Turns the FCIF on/off using command signal. At the same time, it starts up the PLO unit.
Outputs the on/off status of FCIF as a telemetry signal.
Possesses a temperature sensor, and outputs it as a telemetry signal.
(NB 1) All of command signals and control signals are transmitted from the system control/data
processing section. Also, all telemetry signals are output to the system control/data
processing section.
2-4 5
Section 2
(NB 2) When FCIF-A system (B system) is turned off, there is no gate signal to the A system
(B system) of TDA/RDA.
(c) Operating state
Operating states of FCIF are as follows. Also, transition between operating states are shown in
Figure 2.6-7.
1) State 1
FCIF is turned off.
2) State 2
FCIF is turned on, and there is no pulse transmission.
3) State 3
FCIF is turned on, and there is pulse transmission.
4) State 4
Calibration is carried out by the RF signal reflection loop.
State 4
Control signal
Command
State 2
Command
State 1
Figure 2.6-7
2-4 6
FCIF-A
Local Signals
PLO A
PLO B
FCIF-B
Local Signals
2.6.5.5 Others
Thermal control subsystem maintains and controls the temperatures of each part of the precipitation
radar within the tolerance level.
Thermal control method of the precipitation radar is made up of passive thermal control systems
such as MLI, OSR, heat sink, and coating materials, and active thermal control systems such as
heater, and heat pipe. Heater control is by the mechanical thermostat in the panels mounted on the
precipitation radar instruments.
The precipitation radar is thermal controlled on the precondition that it is independently thermal
controlled from the TRMM observatory itself. To carry out independent thermal control, the design
should attempt to avoid heat radiation/heat transfer bonding between the radar and the TRMM
observatory itself as much as possible. For this reason, heat sinking planes are positioned on the
Y plane panels and the antenna section which have a small thermal interference with the TRMM
observatory.
The perimeter of the precipitation radar not positioned within the heat sinking planes are covered
with mutilayer insulation (MLI). Beta cross is used for the outermost layer of the MLI taking into
consideration the anti-atomic oxygen.
Loaded instruments with high calorific value, RF PS and FCIF, are positioned on the +Y plane
2-4 7
Section 2
panel and the -Y plane panel respectively. Because RF PS and FCIF are both of redundant
structure, primary/redundant systems are installed on the same heat sink taking into consideration
the thermal control of the redundant side instruments. The heat from RF PS and FCIF is directly
radiated from the OSR heat sinking plane of the Y plane panels.
The center panel, where transmit/receive electronic instruments such as SSPA, LNA, DIV/COMB
1, DIV/COMB 2, SCDP, and PLO unit are installed, is placed with a heat pipe. This enables a
design with uniform heat distribution within the center panel, and a small heat distortion.
Instrument heat from the center panel is designed to be radiated to space through the heat radiation
bonding with the antenna section. Installed instruments and panel on the installed instruments' side
are coated with black paint to increase the heat radiation bonding.
In the safe hold mode in which loaded instruments are inoperative, a survival heater is employed in
order not to lower the lower limit of the permissible temperature of the loaded instruments. The
survival heater is controlled by a mechanical thermostat.
NS
Ps = Pr + N
Pt
TX
ANT
Gt
PROP
Lp
RAIN
REF
RAIN
(RAIN/EARTH)
Lr
E(Zm/ 0 )
Lr
PROP
ANT
Lp
Gr
2-4 8
RX
2-4 9
Section 2
TRMM Satellite
Precipitation echo
17.04
(NB) The area sampled is the
area symmetrical to both right
and left of nadir. The diagram
shows only one side.
121
327 km
(9.94) (3.55)
X 1
23 km
133
Ground surface
181
189
243
279
389
400
400
18.105
327 km
261
330
23 km
113
184
386
400
Ground surface
238
400
2-5 0
:
Scan angle (measurement value; the definition of sign refers to Figure 2.6-12)
Sx ( ): Rotation matrix when scan angle
TEM: Conversion matrix from the Radar Electric coordinates system to the Radar
Mechanical coordinates system
Based on above formula, the beam direction (Ds) in the Satellite Mechanical coordinates system is
as follows:
DSTASTMADM
TAS:
TMA:
2-5 1
Section 2
The beam track at ground is illustrated in Figure 2.6-13. The error from the cross track occurs
because of the flight velocity of the satellite.
PR
Xe
Ze
Ye
Electric
coordinate
axis
Xm
X0
Zm
Ym
Mechanical coordinate axis
Z0
Y0
Alignment coordinate axis
X S/C
ZS/ C
YS/C
Satellite coordinate axis
Figure 2.6-12
Scan direction
Scan angle
Scan angle
2-5 2
3-1
Section 3
TDRS
TRMM
NASA
NASDA
Earth
Observation
Center (EOC)
Raw Data
Within 48 Hours
After Observation
PR
Level 0 Data
User
User
Within 48 Hours
After Observation
User
GSFC
S ensor
Data Processing
F acility (S DPF)
CERES
Level 0
Data
LIS
Level 0
Data
LaRC
MSFC
TRMM
Science Data
and Information
System (TSDIS)
TRMM
Science
Team
Level 1, 2, 3 Data
User
User
User
Level 1, 2, 3 Data
processing facility, the verification facility and the precipitation radar operations planning facility
set up at the TRMM operations division within the NASDA/EOC, and the Active Radar Calibrator
(ARC) used in western Japan that is permanently set up at the NASDA/EOC. Each facility has an
interface, however are fundamentally independent. There is no computer which manages all
facilities collectively.
3-3
Figure 3.2-1
3-4
SDOC
EOSDIS
EOS Scienc e Data Information System
Product
TRMM
TRMM Operation
Planning Facility
Calibrator
ARC
TRMM Processing
Facility
TRMM PR Data
Processing System
SOCC
SDOC
HK
NRT
CRL
NRT Data
Japan
Me teorological
A gency
TRMM Verificatoin
Facility
HK data
PR L0 data
NRT Data
TMI 1B11
VIRS 1B01
PR Operation Planning
Info rmation
NASA
EOSDIS
Network
SDPF
Science Data
Processing Facility
Raw Data
TSDIS
TRMM Science Data Information System
SOCC
M OC
Mission Operation
Center
Command
W SC
White Sands Center
TDRS
Browse
Work Order
NASDA
EOC
EORC
RESTEC
Product
Order
Users
RESTE C
Product
Users
EOI S
Catalogue Data Distribution System
Catalogue
E OIS
Schedule Management System
Product
E OIS
Media Conversion Subsystem
NASDA/EOC
NASDA/EORC
EOI S
Data Analysis Processing System
Section 3
OUTLINE OF THE GROUND SYSTEMS
U.S.A
TACC
West
Japan
CRL
(Foreign organizations)
JMA
ARC
- Operation planning
software
Precipitation radar
operation planning facility
- Verification control
software
- Calibration software
Verification
facility
- Processing control
software
- PR Level 1 software
- TRMM Level 1&3
software (provision)
Processing facility
3-5
Section 3
Processing
facility
Figure 3.2-3
Verification
facility
Precipitation
radar operation
planning facility
3-6
Processin g Facility
HK data
Processed data
DDS
HK data
Calibra tion data
Pro cessed data
Lev el 0 data
Near r ealtime data
Orb it data
QL
Orbit data
Inspection
Ve rif icat ion
Image displa y
C alibration coefficient
RST
Section 3
3-8
3-9
Section 3
variable angle)
variable angle)
peration
ane l
1510 or less
1760 or less
56 or less
ame
late
00 or less
00 or less
20 or less
aximum dimension of expansion
3-1 0
US
Receiving and
Recording Subsystem
Mission Operation
Management Subsystem
Data Processing
Subsystem
AN
A dvertisement Subsystem
Figure 3.3-1
3-1 1
Section 3
(DDMS)
(DGS)
(MCS)
(DSS)
(DES)
(SMS)
(SMSS)
(IRS)
(URS)
(CADS)
(CATS)
(BDS)
Advertisement Subsystem
(ADS)
3-1 2
(EOIS)
(OLIS)
(DDS)
(NMS)
(DRS)
(EUS)
(CIS)
3-1 3
Section 3
3-1 4
information based on scene information and processing information, and provides the information
to the Catalog Subsystem.
(3) User Request Management Subsystem
The User Request Management Subsystem is the system to receive data orders through the EUS.
The system informs its status for each order based on the user request to the users by online.
3-1 5
Section 3
3-1 6
The following sections provide a brief functional description of the ground system elements
supporting TRMM.
3-1 7
3-1 8
NASDA
EOC
(J apan)
TDRS UPD
TDRS ODMs
TDRS GCMs
TDRS GCMRs
Acquisition Data
TDRS GCMs
TDRS ODMs
R /T Commands
Acquisition Data
NASA/
NASDA
Interface
Point
D efinitiv e TRMM Orb it
Tracking Data
NCC
WSC
T rack ing Da ta
R/T Telemetr y
I-Cha n (32 kbps)
Nascom
TRMM
MOC
S DPF
F DF
T rack ing Da ta
Acquisition Data
Definitiv e T RMM
Orbit and Ancillary Data
TDRS UPD
T DRS Schedule Messag es
TDRS GCMRs
TRMM Command s
ZP Data
GN, DSN,
AGO,
Wallops
Emerg ency
Support
TRMM
TDRS
SCF
LZP D ata
Q/L Data
MOST D AAC
(LaRC) CERES
IST
(MSFC) LIS
SOCC SDOC
STTF
Ground Observation
Da ta
(TSDIS)
PR, TMI, VIRS
Missio n
I nformation
NASDA EOC
(Jap an)
Fligh t Software
Up link/Down link I mag es
Co mmand
Requests
EOSDIS
(GSFC)
Pro duction
Data
G rou nd
Validation
Sites
Section 3
OUTLINE OF THE GROUND SYSTEMS
rodu ction
Data
emote Displays
ttitude Data
Data Quality an d
ccountab ility rep ort
3-1 9
Section 3
3-2 0
Coordination between instrument scientists of TMI, VIRS and PR, and MOC
Provide access to the MOC real-time display
3-2 1
Section 3
3-2 2
telemetry data will be downlinked via WFF. Real-time telemetry will be stripped-and-shipped to
the MOC, in real-time, and recorder playback data will be stored on-site for post-pass playback (to
the MOC and SDPF). TRMM data will be forwarded to the MOC in DDPS 4800-bit Nascom block
format.
3-2 3
Definition
Unprocessed instrument data, time ordered, quality checked, no redundancy.
Ancillary data and georeferencing data attached to Level 0, and processed to sensor-dependent
physical units (e.g. radar reflectivity, brightness temperature)
Meteorological parameters (e.g. rainfall rate) derived from Level 1 data using various
algorithms, which will be produced as a 2-or 3-dimensional rain map along the TRMM swath.
Results of mapping the meteorological parameters (Level 2) on a uniform space and time grid.
4-1
Processing Level
Product
Scene Unit*1
PR
1B21
1 orbit (16/day)
1C21
Radar Reflectivity
1 orbit (16/day)
2A21
1 orbit (16/day)
2A23
PR Qualitative
1 orbit (16/day)
2A25
Rain Profile
1 orbit (16/day)
Monthly Statistics of
Rain Parameter
Monthly Rain Rate
using a Statistical Method
1B11
Brightness Temperature
1 orbit (16/day)
2A12
Rain Profile
1 orbit (16/day)
3A11
VIRS
1B01
Radiance
1 orbit (16/day)
COMB
2B31
Rain Profile
1 orbit (16/day)
3B31
Monthly Rainfall
3A25
3A26
TMI
3B42
3B43
TRMM & IR
Daily Rainfall
TRMM & Other Sources
Monthly Rainfall
Estimated Data
Volume*2
(Compressed)
149 MB
(60~70 MB)
149 MB
(40~50 MB)
10 MB
(6~7 MB)
13 MB
(6~7 MB)
241 MB
(13~17 MB)
40 MB
(26~27 MB)
9.3 MB
(5~6 MB)
14 MB
(14 MB)
97 MB
(6.7~9 MB)
53 KB
(44 KB)
92 MB
(90 MB)
151 MB
(8 MB)
442 KB
(380~410 KB)
242 KB
(110~115 KB)
242 KB
(242 KB)
*1: 1 orbit define from the south end to next south end of each orbit. In almost cases, TRMM product of
which scene unit is one orbit is prepared 16 times in a day. But it is occasionally 15 times in a day.
*2: Estimated data volume, shown in the above table, is corresponding to the version 5 product. It may be
changed due to algorithm version up. Moreover, Zip is applied as compress method of each product.
4-2
Level 1B
VIRS
Level 1A
TMI
Level 1A
PR
Level 1A
1B01
1B11
1B21
TMI
PR
Ca librated
Received Pow er
VIRS
Radi ance
Temperat ures
1C21
PR
Rada r Reflectivity
Level 2
2A12
2A23
2A21
PR
PR Qualitative
PR
Normalized
Radar Surface
Cross Section
2A25
TMI
Ra in Prof ile
PR
3D Rain Profile
B31
C OMB
Rain Profile
Level 3
Level 3
(Combined Product using
TRMM & Other data)
3A11
3B31
3A25
3A26
TMI
Mon thly
Oceanic Rain fall
COMB
Mon thly Rainf all
PR
Mont hly Statistics
of Rain Parameter
PR
Mont hly Rain Rate
usin g a Stat istical Method
3A44
Merged IR Data
3B42
TRMM & IR
Daily Rainf all
GPI
3A46
SSM/I
Monthly Ra infall
3A45
CAMS or G PCC
Rain Gauge
3B43
InfraRed
Global Precipitatio n Ind ex
Special Sensor
Microw ave/Ima ger
CAMS Climate Assessment and
Moni toring System
GPCC Glob al Precipit ation
Climat ology Cen ter
IR
GPI
SSM/I
4-3
4.1.1 PR
Data collected by the precipitation radar (PR) are processed from level 1 to 3. Processing carried
out at each level is explained hereafter. Also, overall flow chart of the PR algorithm is shown in
Figure 4.1-2.
1A21
PR Echo Power (Count Value)
1B21
Calibrated Received Power
Received Power
Noise Power
Minimum Echo Flag
- Rain/No Rain Flag
- Sidelobe Clutter Flag
First Echo Range
(Storm Height)
Range Bin Number
- Surface Peak
- Clutter-free Bottom
- Bottom/Top/Mean of DID
- Ellipsoid
etc.
1C21
Radar Reflectivity (Z Factor)
Z-factor with Rain Attenuation
2A21
Normalized Radar Surface
Cross Section (0)
Normalized Radar Surface
Cross Section
PIA Estimate
etc.
2A25
3D Rain Profile
Rain Rate
2A23
PR Qualitative
Height & Strength of Blight Band
Rain Type
Warm Rain
Rain/No Rain Flag
Freezing Height
Storm Top Height
etc.
- Profile
- Path Average
Attenuation Corrected Z-Factor
etc.
3A26
3A25
Monthly Statistics of
Rain Parameter
4-4
4-5
between processing functions are shown in Figure 4.1-4. The contents of each function are
explained below.
(a) Checking input data
The files specified by the parameter file are checked to see if they can be processed, and if there is
any abnormality, the operator is notified and the processing is terminated. Also, HK data are
isolated by each APID.
(b) Checking the continuity of the packet
The sequence count within the header record of the PR Level 0 data is checked, and the packet is
rearranged in an ascending order. The consistency between the sequence count and the time code
is also checked, and if there is any inconsistency, time correction is carried out.
(c) Extraction of scenes
UTCF is calculated from ACS time and time code stored in the ACS packet. Start/finish time of the
scene information is also converted into a format that is the same as the time code using UTCF and
the leap seconds derived from the scene start time. Based on this information, the science data and
HK data within the PR Level 0 data are sampled.
(d) Conversion to engineering value
PR HK data (RF PS voltage, FCIF temperature, panel temperature, antenna temperature, and
IPSDU current and voltage) within HK data are converted into an engineering value. Data
converted into engineering values are output to HK data file.
(e) Limit check
A limit check is carried out to the data already converted into engineering values, and if they are
outside the limits, the operator is notified of limit abnormality generation. Also, abnormality
monitoring items (CPU RESET FLAG, PHASE CODE ERROR FLAG, RAM CHECK FLAG1,
RAM CHECK FLAG2, RAM CHECK FLAG3, RAM CHECK FLAG4, and T-ROM CHECK
FLAG) are monitored for any abnormality, and if an abnormality is discovered, the operator is
notified of abnormality generation.
(f) Scene editing
If there is a wait file specified by the input parameter file, it is combined with the head of a scene,
and output to a Level 1A file specified by the parameter file.
Scene divided science data and HK data from the same scene, as well as the calibration file
specified by the parameter file are also output to the Level 1A files specified by the parameter file.
Data less than a scene is output to a wait file specified by the parameter file.
4-6
If there is no science telemetry data or HK data that make up the Level 1A file as well as the wait
file, a file which only has the header record of data size 0 is created.
(g) QL data processing
Even if the data specified by the parameter file is QL data, it is possible to edit it to a Level 1A file.
Here, continuity check of the packets is carried out.
Science Data
- Continuity Check
of the Packets
- Extraction
PR HK Data
ACS Ancillary Data
I PSDU Data
HK Data
Data Isolation
Co ntinuity Check
of the Pack ets
Extraction
Engineering Value
PR HK
Conv ersion into
Engineering Values
Limit Check
C alibration
Coeficient
evel 1A
Scen e Editing
4-7
model of the precipitation radar. Longitude and latitude information of ground surface is added to
convert this value into radar reflectivity factor (Z factor) including rain attenuation. Also, rain/no
rain is determined for each angle bin, a flag is set up, and the rain height is calculated. Moreover,
influence of surface clutter, which is mixed from antenna main lobe and side lobe, is evaluated,
and the evaluation result is reflected to the calculation of surface range bin number and the
determination of rain/no rain.
Function structure of 1B21 processing is shown in Figure 4.1-5, and the relationship between the
processing functions is shown in Figure 4.1-6. The contents of each function are explained below.
(a) Editing the observation mode data
Based on the input parameter file name, science telemetry data (for only during observation mode)
for one calibration cycle (3 minutes) as well as HK data already converted into an engineering
value from the Level 1A file are read. If special mode data is contained in the read data, dummy
data is set up. If packet deficit exists within the read calibration cycle, dummy data is set up at the
applicable location. Also, if packet deficit exists at the beginning of a scene, dummy data for an
applicable period is output.
With science telemetry data (special mode), the header section is added, and is output to the
calibration mode data file.
(b) Calculation of radiometric information
PR estimated temperature is calculated from the panel temperature telemetry data already converted
into an engineering value within the read PR HK data. Also, transmission level and transmission
pulse width corresponding to the FCIF estimated temperature are calculated.
Items required for radiometric information (RF PS voltage, temperature telemetry already
converted into engineering values, IPSDU temperature and current, SSPA power monitor,
LOGAMP monitor, and noise level average value) are output to the verification file regulated by
the program.
(c) Calculation of geometric information
Satellite position information during observation time, and position information on the foot print of
each beam angle are calculated based on the orbit data file. Geolocation TOOLKIT provided by
NASA is used for this processing.
(d) Conversion into received power value
A received power vs. count value table considering the gain/loss factor is created to convert the
count value obtained from telemetry data to a received power value. Based on this table, the normal
echo sample of science data, surface echo over sample and rain echo over sample are converted
into received power value.
4-8
4-9
reception level, and the result is reflected in the Level 1B scan status.
(h) Output Data of 1B21 Processing
The outputs of 1B21 processing are listed in below. The received power value and the
transmission power value of the precipitation radar are calibrated periodically by a receiver
calibration software and external calibration experiment, and are meant to correspond to aged
deterioration etc. The values are also changed during calibration coefficient change.
- Meta Data
- PR Calibration Coefficients
- Ray Header
- Scan Time
- Geolocation
- Scan Status
- Navigation
4-10
- Power
4-11
4-12
Temperature Data
Primary Test
System Noise
Normal Sample
Rain Echo
Su rface Echo
Calculation of
Surface Echo
Bin Nu mber of
Clutter-free Bottom
Bin Number of
Top/Bottom/Mean of DID
Bin Number of Ellipsoid
Nav igation
(Location, Velocity
and Attitude of Satellite)
Scan Time
Geolocation In formation
(Longitude & Latiude of
Obs ervation Point)
Satellite Range
Satellite Local Zenith Angle
Catalog
4-13
C1
Z [W]
r2
Z : Radar Reflectivity Factor [mm6 /m3 ] (dBZ = 10log(Z))
Pr : Rain Scattering Received Power (= Received Power System Noise
Where, C1 is a constant (Radar Constant) determined from transmission power, wave length,
pulse width, antenna gain, and so on depending on the radar instrument characteristics, and it is
defined as the following equation.
3 K Pt Gt Gr 1 2 c
10 18
C1 = 10
2
2 ln 2
Moreover, the above radar equation can be expressed by the following equation, in accordance
with the radiometric model shown in the section 2.6.6.1.
Pr = C2 x P x Lr x E[W]
C 2 : Radar Constant P t x Gt0 cos x Gr0 cos
P : Propagation Constant = Lp2 x 4 / 2
Lp = ( / 4 r)2
Lr : Atmosphere (Rain) Attenuation
(Not applicable for 1C21 processing, because rain attenuation is not corrected.)
E : Radar Reflection Component = x c x r2 1 x 2 / 24 x ln2
: Scattering Cross Section per unit volume of a raindrop [m2/m3]
= ( 5 / 4) |K| 2 x Z x 10-18
4-14
The function structure of 1C21 is shown in Figure 4.1-7, and the relationship between the
processing functions is shown in Figure 4.1-8. The contents of the functions are explained below.
(a) Input data check
The scan status of Level 1B product data is determined, and if it is no rain data, it is then converted
into dummy data. Also, if the determined scan status of Level 1B product data is data with a poor
quality (geolocation abnormality), then it is converted into dummy data.
(b) Calculation of Z factor
The radar constant (C1 ) is calculated from the value of 1B21 Ray Header. Rain scattering received
power (Pr) is calculated from the received power and noise level of 1B21, and then a dummy radar
reflectivity factor (Zm) is calculated by using radar equation. The radar reflectivity factor is a
"dummy", because it does not isolate noise deficit during propagation such as atmosphere
attenuation, and because it is calculated in a state that contain these values.
(c) Output Data of 1C21 Processing
The file format is exactly the same as that of 1B21 except for the replacement of the received power
by the radar reflectivity factor including rain attenuation, and noise (no echo range bin) by a
dummy value.
(d) Relationship with Other Algorithms
The output of 1B21 is used for 2A25 and 2B31.
4-15
Dummy Data
Radar Transmissin Power (Pt )
Trans mission P ulse W idth ()
Trans mission Antenna Gain (G t)
Receiving Antenna G ain (G r)
Antenna Beam Width (1)
(Derection for Antenna scan)
Calculation of
Radar Constant
Z factor
including rain attenuation (dBZm)
Normal S ample
- R eliability
Factor
central swath
4 : peak surface return at normally-sampled gate - outside
central swath
iz : Background type
0 : ocean
1 : land
2 : coast
3 : unknown or of a category other than those above or
'mixed' type
: reliability Factor for the PIA estimate, and it is given by
reliabFactor = PIA / std dev(reference value)
where PIA is the 2-way path-integrated attenuation (dB), and
std dev(reference value) is the standard deviation as calculated
from the no-rain sigma-zero values. Both quantities are in
dB. The parameter iw (in Reliable Flag) is determined from
this Factor (Fr) and the S/N ratio (SNR) of the surface return
(in dB).
Fr 3 and SNR > 3
W=1
3 > Fr 1 and SNR > 3
W=2
1 > Fr or (3 > Fr and 3 SNR)
W=3
Fr 3 and 3 SNR W=4
In 2A21 product, moreover, the same information as 1B21 is recorded about Meta data, Scan time,
Geolocation , Scan status and Navigation.
(e) Relationship with Other Algorithms
The output of 2A21 is used for 2A25, 3A25 and 3A26.
(5) 2A23 Processing
(a) Processing Description
2A23 processing is calculate qualitative value for rainfall. Input 1C21 data, output the
determination of rain/no rain and the height of rainfall. In rain, rain type is classified and bright
band is detected. If bright band is detected, its height is calculated. Rain type classification is
carried out based on the vertical profile of Z factor and horizontal distribution of Z factor.
When the bright band exists, rain is classified as stratiform rain. The other type rain is classified as
convective rain and others. If convective rain is existing below the height of freezing level, it is
detected as warm rain (shallow isolated rain).
(b) Input Data of 2A23 Processing
For 2A23 processing, the following input data are read from 1C21.
4-18
- Scan Status
- Geolocation Information
- Minimum Echo Flag
- First Echo Height
- Satellite Range
- Bin Number of Surface Peak
- Range Bin Number of Clutter-free Bottom
- Satellite Local Zenith Angle
- Range Bin Number of Ellipsoid
- Land/Ocean Flag
- Normal Sample
- Surface Oversample
- Range Bin Number of Mean DID
- Meta Data (Observation start/stop time, orbit radius, etc.)
- Ray Header (Start Range Bin Number of Normal Sample, Main-lobe Clutter edge, Side-lobe
Clutter Range)
Additionally, sea surface temperature data (sst-hou data) is used for calculation of freezing level
height.
(c) Output Data of 2A23 Processing
The outputs of 2A23 processing are listed in below.
- Rain Flag
- Rain Type
- Warm Rain
4-19
2
: Shallow isolated (with confidence)
-88 : No rain
-99 : Data missig
- Processing Status
: Status flag for processing of 2A23
0X : Good
1X : Bright band detection may be good.
2X : Rain type classification may be good.
3X : Both bright band detection and rain type
classification may be good.
5X : Not good (because of warnings)
10X : bad (possible data corruption)
-88 : No rain
-99 : Data missig
Where,
X=0 : Over water, X=1 : Over land,
X=2 : Over land/water mixed area, X=9 : Land or Sea error
- Range Bin Number of Bright Band : Range bin number for the height of bright band.
>0
: Range bin number.
= -1111 : No bright band
= -8888 : No rain
= -9999 : Data missing
- Height of Bright Band [m]
: Height of bright band.
>0
: Height of bright band.
= -1111 : No bright band
= -8888 : No rain
= -9999 : Data missing
- Intensity of Bright Band [dBZ]
: Intensity of Z factor in bright band
>0
: Bright band intensity.
= -1111 : No bright band
= -8888 : No rain
= -9999 : Data missing
- Height of Freezing Level [m]
: Height of freezing level estimated from the climatological
surface temperature data (sst-hou data).
>0
: Estimated height of freezing level.
= -5555 : When error occurred in the estimation of freezing
height.
= -8888 : No rain
= -9999 : Data missing
4-20
In 2A23 product, moreover, the same information as 1B21 is recorded about Meta data, Scan time,
Geolocation, Scan status and Navigation.
(d) Relationship with Other Algorithms
The output of 2A23 is used for 2A25, 3A25 and 3A26.
(6) 2A25 Processing
(a) Processing Description
2A25 processing is to calculate Z factor correcting rain attenuation (Ze) for each beam position by
using radar equation. For this calculation, Input data of this calculation is Z factor including rain
attenuation (Zm), scattering cross section of surface, height of freezing level and rain type, and so
on. And then, the vertical profile of rain rate (R) is produced in accordance with the Z-R
relationship (R = a x Zb ) as the fundamental physical parameter of rain. Input 1C21, 2A21 and
2A23, the rain rate estimate is given at each resolution cell (4 km x 4 km x 250 m) of PR, and the
average rain rate estimate between 2 altitude (assumed 2km and 4km) is calculated (path averaged
rain rate). Additionally, the calculation method and calculation accuracy of rain rate is also output.
(b) Input Data of 2A25 Processing
For 2A25 processing, the following input data are read from 1C21, 2A21 and 2A23.
< from 1C21 >
- Scan Status
- Scan Time
- Geolocation Information
- Minimum Echo Flag
- First Echo Height
- Satellite Range
- Bin Number of Surface Peak
- Range Bin Number of Clutter-free Bottom
- Range Bin Number of Ellipsoid
- Satellite Local Zenith Angle
- Normal Sample
- Ray Header (Start Range Bin Number of Normal Sample, Main-lobe Clutter edge, Side-lobe
4-21
Clutter Range)
< from 2A21 >
- PIA
- Reliability Flag
- Reliability Factor
- Sigma Zero
< from 2A23 >
- Rain Type
- Warm Rain
- Processing Status
- Height of Freezing Level
- Height of Bright Band
(c) Output Data of 2A25 Processing
The outputs of 2A25 processing are listed in below.
- Clutter Flag
4-22
for each angle bin, and it is constantly used for all ranges in
one angle bin.
: Range bin numbers of the nodal points at which the
attenuation parameter alpha is given. In no-rain angle bins,
this parameter is set to 0.
: Z factor correcting rain attenuation. If the input radar
- Epsilon ()
- Error Estimate of Rain [dB]
- Error Estimate of Z Factor [dB]
- Method
- Near Surface Rain Rate
- Rain Flag
- Range Bin Number
- Reliability Flag
- Thickness of PIZ
- Weighting Factor
4-23
- xi ()
- zeta ()
- Average of zeta
- Standard Deviation of zeta
- Maximum of Z Factor [dBZ]
- Rain Rate Parameter (a)
In 2A25 product, moreover, the same information as 1B21 is recorded about Meta data, Scan time,
Geolocation, Scan status and Navigation.
(d) Relationship with Other Algorithms
The output of 2A25 is used for 3A25 and 3A26.
(7) 3A25
(a) Processing Description
3A25 processing is to compute the monthly average of rain parameter in lon./lat.5 x 5 and 0.5 x
0.5 region using 1C21, 2A21, 2A23 and 2A25. The representative outputs are monthly average
of rain rate (mm/h) in lon./lat.5 x 5 region at 5 layers (altitude 2 km, 4km, 6km, 10km and
15km) and at path average, and monthly average rain rate (mm/h) in lon./lat.0.5 x 0.5 region at 3
layers (2 km, 4 km and 6 km) and path average. Additionally, probability of rain parameters,
average, standard deviation, histograms and correlation coefficients of rain parameters are output.
(b) Input Data of 3A25 Processing
For 3A25 processing, the input data are read from 1C21, 2A21, 2A23 and 2A25.
4-24
4-25
Moreover, the difference among quantities of the following kind can be calculated.
Pr (stratiform rain / rain)
Pr(stratiform rain / rain)
Pr(stratiform rain / rain)
= Stratiform Rain Pixel (at an layer) / Rain Pixel (at same layer)
= Stratiform Rain Pixel (at an layer) / Rain Pixel (path average)
= Stratiform Rain Pixel (path average) / Rain Pixel (path average)
Pr corresponds to what is the most common definition of the probability of stratiform rain:
given that rain is present, what is the probability that it is stratiform. Pr is the probability that,
given rain is present at a particular height level, that the rain is stratiform. Pr is the probability,
given that rain is present somewhere along the beam, that rain is present at particular height and
that the rain is stratiform.
b. Means and Mean Square
< Rain Rate Parameters >> [mm/h]
The following parameters are output for both 5 x 5 and 0.5 x 0.5 grid.
- Rain Rate
- Stratiform Rain Rate
- Convective Rain Rate
- Surface Rain Rate
- Surface All Rain Rate
4-26
- HB PIA
< Height of Bright Band, Height of Storm Top, Snow Depth, etc.>> [m]
The following parameters are output for both 5 x 5 and 0.5 x 0.5 grid.
- Height of Bright Band
- Height of Storm Top
- Snow Depth
The following parameters are defined as output of 5 x 5 grid, but these are not calculated at
present (version 5 products).
- ZPZM
- Width of Bright Band
4-27
- xi ()
- NUBF Correction Factor
- Epsilin ()
c. Histograms
Histograms are simple count, which is classified by using 31 designed threshold value, and
calculated for only 5 x 5 grid.
- Rain Rate
- Stratiform Rain Rate
- Convective Rain Rate
- Surface Rain Rate
- Surface All Rain Rate
- Un-corrected Z (Zm)
4-28
- Maximum Z (Zmax )
- SRT PIA
- HB PIA
- 0th -Order PIA
- 2A25 PIA
The following parameters are defined as output of 5 x 5 grid, but these are not calculated at
present (version 5 products).
- ZPZM
- Vertical Gradient of Zm
d. Correlation Coefficients
The following parameters are calculated only when rain rates at 2 km, 4 km and 6 km are all nonzero and are output for only 5 x 5 grid.
- Rain Rate
: Correlation coefficient of rain rate at height: (2 km, 4 km),
(2 km, 6 km), (4 km, 6 km) for all rain type.
- Stratiform Rain Rate
: Correlation coefficient of rain rate at height: (2 km, 4 km),
(2 km, 6 km), (4 km, 6 km) for stratiform rain.
- Convective Rain Rate
: Correlation coefficient of rain rate at height: (2 km, 4 km), (2
km, 6 km), (4 km, 6 km) for convective rain.
4-29
The following parameters are calculated for only 5 x 5 grid, only when all 3 PIAs exist and are
reliable or marginally.
- PIA
The following parameters are defined as output of 5 x 5 grid, but these are not calculated at
present (version 5 products).
- Xi / Zm
- Storm Top Height / Zm
In 3A25 product, moreover, the same information as 1B21 is recorded about meta data (Core meta
data and PS meta data).
(d) Relationship with other algorithms
3A25 is the final product and is not input to any other algorithms.
(8) 3A26
(a) Processing Description
3A26 processing is to compute monthly rainfall, rain rate averages, rain rate standard deviation and
probability distribution function, for 5 x 5 grid at 3 layers (2 km, 4 km and 6 km) and path
average by Multiple Threshold Method using 1C21, 2A21, 2A23 and 2A25.
(b) Input Data of 3A26 Processing
For 3A26 processing, the input data are read from 1C21, 2A21, 2A23 and 2A25.
(c) Output Data of 3A26 Processing
As 3A26 output, the following data is calculated in lon./lat. 5 x 5 region (grid). These grids
cover the area of 40 N ~ 40 S x 180 E ~ 180 W, and the number of grid is 16 x 72.
a. Probabilities of Rain
- Total Counts
- Rain Counts
4-30
reflectivity factor (Zm) with physical significance, in contrast to telemetry data which is count
values. This data becomes the basis for all analyses, with precipitation characteristics actually
only becoming clearer after data has been analyzed with Level 2 processing.
Level 2 processing results (2A21, 2A23, 2A25) give the precipitation characteristics of each IFOV,
and these are the interest values for scientific purposes. They are useful when information on
rainfall, such as 3-D structure of rain rate, types of rain, height of rainfall and so on, are desired.
Level 3 processing results (3A25, 3A26) provide monthly statistics of rain distribution and so on,
and they are useful when statistical values are desired.
4.1.2 TMI
TMI Data Products and outline of their algorithms are explained below. The structure of each
product is described in the later section (4.2.4.2).
Level
1B-11
2A-12
TMI Rain Profile, which is given for each pixel at vertical 14 layers, and
consists of several physical parameters, such as cloud water, precipitation
water, cloud ice, precipitation ice and latent heating. In this product,
moreover, intensity of surface rain and convective rain, and its reliability
factors are included.
3A-11
4-32
4-33
4-34
Procedures are then employed to either interpolate the pixel value based upon neighbors or to set
the pixel to missing. Neighboring pixels as well as minimum rms are used to make this decision.
(c) Input Data of 2A12 Processing
For 2A12 processing, 1B11 is input, and the following reference data are used.
< Supplied by TSDIS >
- Land/Ocean database with 4 km resolution
- Topographic database with 4 km horizontal./200 vert. res.
< Supplied within algorithm >
- Climatology of Sea Surface Temp. - 1 file ~ 300 Kbytes
- Database of cloud-only profiles - 6 files ~ 15 Kbytes
- Database of cloud model profiles - 6 files ~ 30 Mbytes
All the files listed above are accessed every time the algorithm is invoked. The files do not change
with time, except at new algorithm releases. The files must therefore be stored at TSDIS
permanently but there is not distribution requirement.
(d) Output files
The outputs of 2A12 processing are listed in below.
- Data Flag
- Rain Flag
- Surface Flag
: The data flag indicates the quality of data. and has the
following values.
0 : Good data quality
-9 : Channel brightness temperature outside valid range
-15 : The neighboring 5 x 5 pixel array is incomplete due to
edge or bad data quality.
-21 : Surface type invalid
-23 : Date time invalid
-25 : Latitude or longitude invalid
: The Rain Flag indicates if rain is possible. If the value is
greater than or equal to zero rain is possible. If the value is
less than zero the pixel has been pre-screened as nonraining.
: The Surface Flag indicates the type of surface and has the
following values.
0 : Water
4-35
1 : Land
2 : Coast (land and ocean is mixed)
3 : Others
- Surface Rain [mm/h]
: The Surface Rain is the instantaneous rain rate at the surface
for each pixel.
- Convective Surface Rain [mm/h] : The Convective Surface Rain is the instantaneous convective
rain rate at the surface for each pixel.
- Confidence [K]
: The Confidence is that associated with the surface rain. It is
measured as an rms deviation in temperatures with units in
degrees (K).
3
- Cloud Liquid Water [g/m ]
: This is the cloud liquid water content for each pixel at 14
layers.
3
- Precipitation Water [g/m ]
: This is the precipitation water content for each pixel at 14
layers.
3
- Cloud Ice Water [g/m ]
: This is the cloud ice water content for each pixel at 14 layers.
3
- Precipitation Ice [g/m ]
: This is the precipitation content for each pixel at 14 layers.
- Latent Heating [C/h]
: This is the latent heating release (C/day) for each pixel at 14
layers.
In 2A12 product, moreover, the same information as 1B11 is recorded about Meta data, Scan time,
Geolocation, Scan status and Navigation.
(e) Relationship with Other Algorithms
The output of 2A12 is used for 2B31, 3B31 and 3B42.
4-36
4km DB
Water
a simple regression
type of algorithm
Land/Mixed/Others
topographic
data base
Clear sky
Caliculate Total Vaper
Volume
Cloud check
unretrieved flag on
4-37
- Land-water mask data file (The spatial resolution should be the same order as the TMI resolution
and will be provided by the TMI team)
- Climatological freezing height information (The spatial resolution will be 5x5 and will be
provided by the TMI team)
(d) Intermediate data
Rain rate/Brightness temperature histograms
(e) Output data
As 3A11 output, the following data is calculated in lon./lat. 5 x 5 region (grid). These grids
cover the area of 40 N ~ 40 S x 180 E ~ 180 W, and the number of grid is 16 x 72. The land
pixels are filled by -9999.
- Monthly Rainfall [mm]
- Number of Samples
- Chi Square Fit
4.1.3 VIRS
VIRS Data product and outline of its algorithm is explained hereafter. The structure of 1B01
product is described in the later section (4.2.4.3).
4-38
Level
1B01
- Geolocation
- Scan Status
- Navigation
- Solar Cal
- Calibration Counts
- Temperature Counts
4-39
4.1.4 COMB
COMB products are combined PR and TMI data products. COMB data products and their
algorithm is explained hereafter.
Level
2B31
3B31
COMB Monthly Rainfall uses the high-quality retrievals done for the
narrow swath in combined 2B31 data to calibrate the wide swath retrievals
generated in TMI 2A12 data. It calculates monthly accumulated rainfall at each
5 x 5 grids for near surface and 14 vertical layers.
3B42
3B43
4-40
- Epsilon [dB]
- R-hat [mm/h]
- PIA [dB]
- TMI-PIA [dB]
- RR-Surf
4-41
For each 5 x 5 grid, an adjustment ratio will be calculated from the swath overlap region which
will then be applied to the 2A12 product in order to produce monthly means. Detailed
coregistration is not necessary since the overlap in the swaths corresponds to pixel numbers 79129 of the TMI.
The algorithm is divided into two modules. The first module is used to derive the adjustment ratios.
a. Module 1:
1) Initialize all sums
2) Ingest 2A12 and 2B31 overlap region The details depend upon TSDIS, but the algorithm needs
the orbit numbers for first and last orbit of the month
3) Derive adjustment ratios
b. Module 2
The second module consists of adding the TMI 2A12 and then applying the adjustment ratio
1) Sum the hydrometeors while counting the number of overpasses
2) Calculate monthly accumulations
3) Apply adjustments
4) Write output
(b) Input Data of 3B31 Processing
For 3B31 processing, TMI 2A12 and PR 2B31 are input, and the following reference data is
necessary for processing of TMI data.
< Supplied by TSDIS >
- Land/Ocean database with 4 km resolution
(c) Output Data of 3B31 Processing
The outputs of 3B31processing are listed in below.
- Surface Rain (TMI) [mm]
4-42
4-43
TMI precipitation data is completed for the orbit, the orbit averages of the accumulated VIRS and
TMI precipitation rate data are computed and then clipped to coincident observations. These
clipped precipitation rate and observation count data are then added to the (calendar) monthly
clipped VIRS and clipped TMI data accumulator files, respectively. The orbit average unclipped
TMI precipitation rate and observation count data are added to the (calendar) monthly unclipped
TMI data accumulator file (this file is used for 3B43 processing).
When the month period flag is set to END in accordance with the calendar month specified
TSDIS scheduler, and the end-of-orbit processing has been completed, 3B42 software computes
the calendar monthly averages of the clipped VIRS, clipped TMI, and unclipped TMI precipitation
data. And then, 3B42 software reads the product 3B31, which is in HDF, extracts the TMI/TCI
(TRMM Combined Instrument) calibration parameters, interpolates them to the 1 resolution, and
multiplies them by the monthly average clipped TMI data to obtain the monthly average clipped
TCI precipitation and observation count data. The monthly average clipped VIRS and TCI
precipitation and observation count data are then used to compute the calendar month IR calibration
parameters
b. Adjustment of Merged-IR Precipitation & Estimation of RMS Error
The merged-IR data are supplied at the 1 spatial resolution and the one-day temporal resolution in
5-day (pentad) spans.
3B42 software extracts the specified day of merged-IR data from the flat binary pentad file. The
day of merged-IR data is then calibrated to the bias of the VIRS data. A calendar month of
multiplicative IR calibration parameters are then read and used to adjust the day of merged-IR
precipitation rate data. After the precipitation rate data have been adjusted, a corresponding RMS
precipitation-error estimate is calculated.
(b) Input Data of 3B42 Processing
For 3B42 processing, 3B42 (including intermediate product of uuclipped TMI), 3B31, 3A46
(SSM/I estimate) and 3A45 (Rain gauge) are input.
(c) Output Data of 3B42 Processing
The outputs of 3B42processing are listed in below.
- Precipitation [mm]
- Relative Error
4-44
All input data sources are on the calendar month temporal resolution with the exception of the
adjusted merged-IR data, which is on the pentad (5-day) resolution. To obtain the requisite
calendar month average of adjusted merged-IR data, 3B43 averages the adjusted merged-IR
pentads that span the calendar month of interest. Also, prior to combination with the SSM/I,
adjusted merged-IR, and rain gauge data, the monthly average unclipped TMI data is converted
(calibrated) to TRMM Combined Instrument (TCI) data using the TMI/TCI calibration parameters
from Product 3B31. After the preprocessing is complete, the four independent precipitation
fields are merged together to form the best-estimate precipitation rate and RMS precipitation-error
estimates
(b) Input Data of 3B43 Processing
For 3B43 processing, TMI 1B01, 2A12 and COMB 3B31 and Merged IR data (3A44) are input.
Additionally, GPI is used to convert VIRS radiance to precipitation rate.
(c) Output Data of 3B43 Processing
The outputs of 3B43 processing are listed in below.
- Precipitation [mm]
4-45
- Relative Error
4.1.5 CERES
CERES data products and their algorithm are explained hereafter.
a.
4-46
4-47
Name
Level
Description
CER01
BDS
L1B
CER02
ES-8
L2
CER13
ES-4
L3
CER14
ES-4G
L3
CER03
ES-9
L3
CER11
SSF
L2
Single Satellite Flax (FOV radiance, clear area radiance, cloudy area radiance
and cloud properties)
CER04
CRS
L2
Cloud Radiative Swath (surface flux, internal atmosphere flux, TOA flux)
(SARB modeling method)
CER05
FSW
L3
CER07
SYN
L3
CER08
AVG
L3
CER15
ZAVG
L3
CER12
SFC
L3
CER06
SRBAVG
L3
CER16
CRH
L3
CER06
MOA
L3
surface fluxes
clouds
4-48
Figure 4.1-11 The scan pattern of two CERES scanners on EOS-AM and EOS-PM spacecraft.
(2) Subsystem 2: ERBE-Like Inversion to Instantaneous TOA Fluxes
The ERBE-like inversion subsystem converts filtered CERES radiance measurements to
instantaneous radiative flux estimates at the TOA for each CERES field of view. The basis for this
subsystem is the ERBE Data Management System which produced TOA fluxes from the ERBE
scanning radiometers onboard the ERBS (Earth Radiation Budget Satellite), NOAA-9 and NOAA10 satellites over a 5-year period from November 1984 to February 1990 (Barkstrom 1984;
Barkstrom and Smith 1986). The ERBE Inversion Subsystem is a mature set of algorithms that
has been well documented and tested. The strategy for the CERES ERBE-like products is to
process the data through the same algorithms as those used by ERBE, with only minimal changes,
such as those necessary to adapt to the CERES instrument characteristics.
(3) Subsystem 3: ERBE-Like Averaging to Monthly TOA
This subsystem temporally interpolates the instantaneous CERES flux estimates to compute
ERBE-like averages of TOA radiative parameters. CERES observations of SW and LW flux are
time averaged using a data interpolation method similar to that employed by the ERBE Data
Management System. The averaging process accounts for the solar zenith angle dependence of
albedo during daylight hours, as well as the systematic diurnal cycles of LW radiation over land
surfaces.
The averaging algorithms produce daily, monthly-hourly, and monthly means of TOA and surface
SW and LW flux on regional, zonal, and global spatial scales. Separate calculations are performed
for clear-sky and total-sky fluxes.
4-49
4-50
4-51
5.
6.
Regionally and temporally sort and merge the gridded cloud and radiation data produced by
subsystem 6
Regionally and temporally sort and merge the near-synoptic geostationary data
Interpolate cloud properties from the CERES times of observation to the synoptic times
Interpolate cloud information and angular model class, convert the narrowband GOES
radiance to broadband (using regional correlations to CERES observations), and then convert
the broadband radiance to broadband TOA flux (using the CERES broadband ADMs)
Use the time-interpolated cloud properties to calculate radiative flux profiles as in subsystem 5,
using the synoptic TOA flux estimates as a constraint
Use the diurnal shape of the radiation fields derived from geostationary data, but adjust this
shape to match the CERES times of observations (assumed gain error in geostationary data)
The system described above could also use the ISCCP geostationary cloud properties. The
disadvantage of this approach is that it incorporates cloud properties which are systematically
different and less accurate than those from the cloud imagers flying with CERES. The ISCCP
cloud properties are limited by geostationary spatial resolution, spectral channels, and calibration
accuracy. In this sense, it would be necessary to calibrate the ISCCP cloud properties against the
TRMM and EOS cloud properties. We are currently performing sensitivity studies on the utility of
the ISCCP cloud properties for this purpose.
(8) Subsystem 8: Monthly Regional, Zonal, and Global Radiation Fluxes and Cloud
Properties (ATMOSPHERE Data Product)
This subsystem uses the CERES instantaneous synoptic radiative flux and cloud data (subsystem
7) and time averages to produce monthly averages at regional, zonal, and global spatial scales.
Initial simulations using both 1-hourly and 3-hourly data have shown that simple averaging of the
3-hourly results is adequate for calculating monthly average LW fluxes. SW flux averaging,
however, is more problematic.
The magnitude of the solar flux diurnal cycle is 10 to 100 times larger than that for LW flux. Two
methods for SW time averaging are currently being tested using Release 2 data. The first method
uses the same techniques as subsystem 7, but to produce 1-hourly instead of 3-hourly synoptic
maps. Time averaging then proceeds from the 1-hourly synoptic fields. The second method starts
from the 3-hourly synoptic data, and then time interpolates using methods similar to ERBE for
other hours of the day with significant solar illumination. While the use of models of the solar
zenith angle dependence of albedo are adequate for TOA and surface fluxes, we will examine
extensions of these techniques to include interpolation of solar absorption within the atmospheric
column. A key issue is to avoid biases caused by the systematic increase of albedo with solar
4-52
zenith angle for times of observation between sunset and sunrise and the first daytime observation
hour.
(9) Subsystem 9: Grid TOA and Surface Fluxes for Instantaneous Surface Product
(SURFACE Data Product)
This subsystem is essentially the same process as in subsystem 6. The major difference is that
instead of gridding data to be used in the Atmosphere Data Products (subsystems 5, 6, 7, and 8),
this subsystem spatially grids the data to be used in the Surface Data Products (subsystems 9 and
10). The spatial grid is the same: 1.0 degree equal angle. See the data flow diagram (Figure 4.110).
(10) Subsystem 10: Monthly Regional TOA and Surface Radiation Budget
(SURFACE Data Product)
The time averaging for the Surface Data Product is produced by two methods. The first method is
the same as the ERBE method (ERBE-like product in subsystem 3) with the following exceptions:
Improved CERES models of solar zenith angle dependence of albedo
Improved cloud imager scene identification (subsystem 4) and improved CERES ADMs to
provide more accurate instantaneous fluxes
Simulation studies indicate that the monthly averaged fluxes will be a factor of 2-3 more accurate
than the ERBE-like fluxes
The second method incorporates geostationary radiances similar to the process outlined for
synoptic products in subsystem 7. We include this method to minimize problems during the initial
flight with TRMM when we have only one spacecraft with two samples per day. As the number of
satellites increases to 3, the geostationary data will have little impact on the results.
Because one of the major rationales for the Surface Data Products is to keep surface flux estimates
as closely tied to the CERES direct observations as possible, this subsystem will not calculate inatmosphere fluxes, and will derive its estimates of surface fluxes by the same methods discussed
in subsystem 4.6.
(11) Subsystem 11: Grid Geostationary Narrowband Radiances
CERES will use 3-hourly geostationary radiance data to assist diurnal modeling of TOA fluxes and
to minimize temporal interpolation errors in CERES monthly mean TOA flux products. This
subsystem is essentially the same process as in subsystem 6. The major difference is that the
process is performed on geostationary radiances instead of CERES TOA fluxes. The current input
data are one month of 3-hourly ISCCP B1 geostationary (GEO) data which contain visible (VIS)
and infrared (IR) narrowband radiances from different satellites. At the present time, GEO data are
available for four satellites; METEOSAT, GOES-East, GOES-West, and GMS. The spatial
resolution of the GEO data set is approximately 10 km. These data are gridded and spatially
4-53
averaged into CERES 1-degree equal-angle grid boxes using functions described in subsystem 6.
The outputs consist of mean and statistics of VIS and IR narrowband radiances for each of the
CERES 1-degree grid box and each of the 3-hourly synoptic time. This data product represents a
major input source for both subsystem 7 and 10.
(12) Subsystem 12: Regrid Humidity and Temperature Fields
This subsystem describes interpolation procedures used to convert temperature, water vapor,
ozone, aerosols, and passive microwave column water vapor obtained from diverse sources to the
spatial and temporal resolution required by various CERES subsystems. Most of the inputs come
from EOS DAO or NOAA NCEP analysis products, although the subsystem accepts the inputs
from many different sources on many different grids. The outputs consist of the same
meteorological fields as the inputs, but at a uniform spatial and temporal resolution necessary to
meet the requirements of the other CERES processing subsystems. Interpolation methods vary
depending on the nature of the field. For Release 2, CERES is planning to use the DAO analysis
products. One of the key issues for use of analysis products in a climate data set is the freezing
of the analysis product algorithms during the climate record. DAO has agreed to provide a
consistent analysis method for CERES.
4.1.6 LIS
LIS data products and their algorithm is explained hereafter.
4-54
Class
Orbit
Browse
Orbit Attribute
Orbit Summary
Browse Area
Vector Statistics
Image Attributes
Background
Area
Flash
Group
Event
Flash density
View Time
One Second Data
Meta Data
4-55
from extremely low frequency (ELF) radio waves to x-rays. One of the strongest radiation regions
is in the optical wavelengths with peak power typically between 100 to 1000 MW. These optical
emissions result from the dissociation, excitation, and subsequent recombination of atmospheric
constituents as they respond to the sudden heating in the lightning channel.
It is important to stress that, while the cloud significantly alters the temporal characteristics of the
cloud top optical signals, the cloud does not block these emissions. When viewed from above, the
optical lightning signals appear as a diffuse light source radiating from the cloud top.
Measurements of the total optical energy radiated from the cloud top are in good agreement with
ground-based measurements of cloud-to-ground flashes and support the theory that the cloud acts
like a conservative scatterer, i.e., that most of the optical energy escapes the cloud.
LIS is a sensor which observes near IR spectrum created by lightning over the cloud. LIS data
products and their algorithm is explained hereafter.
(1) Definitions
The basic science data product of LIS is lightning. This product is comprised of several
components, including: raw data (level 1-A), background images (level 1-B), events (level 1-B),
groups (level 2), flashes (level 2), areas (level 2), vector data (level 2), browse data (level 3), orbit
statistics (level 3), flash density maps (level 4), and metadata. Before we can discuss the details of
the various components, we must define each of the underlying data storage classes that drive the
algorithm. These data storage classes are backgrounds, events, groups, flashes, areas, and orbits.
(a) Background
A background image is a "snap shot" of the background estimate created by the LIS Real Time
Event Processor (RTEP). The background data consists of 12 bit raw count amplitudes at each of
the 128x128 pixel locations and the time at which the background image was taken. The
background is identified as LIS02. The background is transmitted in the data stream along with
event data to maintain the average transmission rate. When the transmission of one background is
begun, the next background image is captured. New images are sent to the ground as frequently as
the event load and transmission rate allow.
(b) Event
An event is defined as the occurrence of a single pixel exceeding the background threshold during
a single frame. In other words, each pixel output from the RTEP produces a separate event. The
raw LIS instrument data consists of time, x and y pixel locations, and amplitude of the event. An
event is the basic unit of data from the LIS. An event is identified as LIS03.
Although an event can be thought of as a single optical pulse due to lightning, it is possible that
4-56
multiple pulses occurring within the 2 ms integration window may contribute to an event.
Therefore, we purposely did not use pulse or stroke (or other similar name) to describe the
basic unit of data from the LIS (Note: an event may sometimes not be due to lightning at all. It may
be produced by noise in the analog data stream exceeding the background threshold. In that case,
the event is a false alarm).
(c) Group
Because a single pixel will almost never correspond to the exact cloud illumination area, a lightning
discharge will often illuminate more than one pixel during a single integration time. The result is
two or more adjacent events at the same time frame. When these multiple events are adjacent to
each other (a side or corner of the events touching), they will be placed in a single group. The
formal definition of a group is one or more simultaneous events (i.e., events that occur in the same
time integration frame) that register in adjacent (neighboring or diagonal) pixels in the focal plane
array. A group may consist of only one event or include many events. The location data for a
group will be calculated in earth-based (latitude/longitude) coordinates. This is done to provide
consistent representation in the group/flash/area processing and because the ultimate goal of the
analysis to locate lightning with respect to the earths surface. A group is identified as LIS04.
Although a group may often correspond to a single lightning optical pulse, it is also possible that
multiple lightning pulses occurring within the 2 ms integration window may contribute to a group.
A false event due to noise at a pixel exceeding the background threshold can also contribute to a
group (although noise groups often contain only one event).
(d) Flash
A lightning flash consists of one to multiple optical pulses that occur in the same storm cell within
a specified time and distance. A lightning flash should then correspond to several related groups in
a limited area. For the LIS algorithm, we define a flash as a set of groups sequentially separated in
time by no more than 330 ms and in space by no more than 5.5 km. The temporal and spatial rules
can be easily adjusted in the LIS algorithm processing software.
We will continue to examine the rules closely during the analysis of OTD and early LIS data to
fine tune the rules defining a flash. A flash may include as few as one group with a single event
or it may consist of many groups, each containing many events. Since there is the possibility that
the TRMM satellite will move a significant fraction of a pixel during the time of a flash, spatial
characteristics for a flash (and all higher level parameters) are calculated in ground coordinates (i.e.,
latitude and longitude resolution). A flash is identified as LIS05. We have used the term flash for
this data category because we believe that, as it has been defined above, the resultant flash will
generally correspond to the accepted definition of a conventional lightning flash. Note that with
LIS data alone, we cannot determine if a flash is a ground or cloud flash. It is possible that future
versions of the LIS algorithm may incorporate data from ground flash locating systems to help
4-57
interpret LIS flashes. We do acknowledge that, on occasion, distinct conventional lightning flashes
may result in a single flash being produced by the LIS algorithm (e.g., possibility in high flashing
rate mesoscale convection systems). Other mismatches between algorithm flashes and actual
conventional flashes will undoubtedly also occur. Note that there is no absolute time limit to a flash.
That is, as long as subsequent groups are produced in an area within the 330 ms time windows, all
groups will be assigned to a single flash.
(e) Area
Lightning is produced in thunderstorm cells that have dimensions of about 10 km by 10 km. Many
storms, however, are multicellular and may extend over large areas and exist for many hours.
Individual storms generally last much longer than the LIS will view them. Therefore, we define an
area as a near contiguous region on the surface of the earth that has produced lightning (defined as
a set of LIS flashes) during a single orbit of the LIS. An area thus defined consists of a set of
flashes separated in space by no more than 16.5 km (approximately 3 pixels). The spatial rule can
be easily adjusted in the LIS algorithm processing software if necessary after analysis of OTD
and/or LIS data. An area may include many flashes or contain as few as one event (i.e., one flash
consisting of one group which in turn consists of one event). There is no interflash or absolute
time limit rule being imposed in the area definition since, as noted previously, the LIS viewing
time is much shorter than storm life cycle. Although there is no explicit limit to the temporal
duration of an area (i.e., as long as there are events/groups/flashes in the region, all will be
assigned to the area), the LIS instrument will only view any ground location within its FOV for a
maximum of 80 seconds. Therefore, area duration will generally not exceed 80 seconds except
possibly for very extensive (and very active) mesoscale storm complexes. An area is identified as
LIS06. The area definition serves as a proxy for a thunderstorm, however, due to the nature of the
algorithm and possible spatial and temporal distribution of the data, several storms may be
combined into one area. It is also possible for a single thunderstorm to be divided into more than
one area. More sophisticated algorithms (with input from external ground-, airborne-, and spacebased observing systems) will be needed to more precisely determine thunderstorms in the LIS
data.
(f) Orbit
The data granule for TRMM has been established as one orbit. Thus, all data from the LIS is
stored and summarized at the orbit granule. However, the beginning and end times of the LIS orbit
granule differ from the TRMM defined orbit. Since dividing the LIS data at the equatorial crossing
would often split storms, the LIS orbit granule is defined to begin and end at the latitude of the
southernmost part of the orbital path. This location is often away from lightning producing tropical
convection. This should lessen the probability that users will have to acquire more than one orbit to
study specific lightning systems. An orbit will include every area with latitudes contained within
4-58
the geographic boundaries of the orbit. All flashes, groups, and events associated each area in an
orbit will be kept with the orbit regardless of where they were located. Background images
occurring between the start and stop location of the orbit will also be kept with the orbit. An orbit
is identified as LIS07.
Since orbits will have a geographic start and stop at the southernmost location of the orbit, it is
possible for flashes, groups and events to be on the opposite side of the orbit boundary from the
parent areas. This will occur if the areas were active at the time of the orbit boundary crossing.
Since all of the LIS lightning data is associated with the parent area, all child data (flashes, groups,
and events) will be kept in the orbit with the parent area.
(g) View Time
Unlike many of the other instruments on TRMM, the LIS data is very dependent on how long a
particular location was viewed by the LIS instrument. For a single pass, different locations on the
ground can have a wide range (0 to 80+ seconds) of view times. The amount of lightning in a
location is not very useful without information on how long it took to produce that amount of
lightning. To provide this information to the users of the LIS data, view time information is
calculated for each point along the LIS field of view.
(h) One Second Data
The LIS data are also very dependent on the status of the LIS instrument. The one second data
provides this information as a series of one second snapshots of internal and external instrument
parameters .
(2) Algorithm Mathematical Description
(a) Example Data Processing Sequence
The purpose of this section is to graphically describe the algorithm that accumulate the individual
LIS events into groups, flashes, and areas by walking through a typical LIS data scenario. In
this illustrative exercise, all times indicated are times after the first event time. Numbers indicate
event numbers while lowercase letters represent the groups. The flashes are designated by capital
letters and the areas are indicated by Greek letters. Each subsequent section describes how the
algorithm processes the events that occurred at that integration time. For the purpose of this
demonstration, it is assumed that there were no events prior to the events at time 0 and that the
pixel grid is 0.02 wide in latitude and longitude. In general, the latitude/longitude grid in earthbased coordinates and the pixel grid will not be the same size or coregistered. In addition, the times
will be time from the start of the orbit.
a. Time = 0 ms
The first time integration is shown in Figure 4.1-13. Three (1,2,3) events occur at this time
4-59
integration. Since the events are simultaneous and register in adjacent (i.e., neighboring or
diagonal) pixels, they are collected into a single group (a). The group is assigned a new parent
flash (A) and the new flash is assigned a new parent area ().
4-60
c. Time = 350 ms
The next integration time with data is shown in Figure 4.1-15. The time is 350 ms after the time of
the first events, but only 250 ms after the time of the last events. At this time there are four
(7,8,9,10) more events. Events 7 and 8 are adjacent to each other and are assigned to a new group
(c). Events 9 and 10 are not adjacent to events 7 and 8, but are adjacent to each other. They are
assigned to another new group (d). Since group c is within 330 ms of the last group of flash A
(250 ms) and is also within 5.5 km of the parts of flash A, group c is assigned to flash A and area
. Although group d also occurred within 330 ms of the last group of flash A, it is greater than
5.5 km away from any part of flash A so it is assigned to a new flash (B). The parts of flash B
(i.e., group d) are greater than 16.5 km away from any part of area so flash B is also assigned a
new area ().
4-61
4-62
start_time
0
350
700
delta_time
700
50
0
event_count
7
4
1
latlon_count
6
4
1
child_count
2
1
1
child_ids
A,C
B
D
parent_id
a
b
a
g
start_time
0
350
700
700
delta_time
350
50
0
0
event_count
6
4
1
1
latlon_count
6
4
1
1
child_count
3
3
1
1
child_ids
a,b,c
d,e,f
g
h
parent_id
A
A
A
B
B
B
C
D
group_time
0
100
350
350
400
400
700
700
event_count
3
3
2
2
1
1
1
1
latlon_count
3
3
2
2
1
1
1
1
child_count
3
3
2
2
1
1
1
1
child_ids
1,2,3
4,5,6
7,8
9,10
11
12
13
14
4-63
4-64
Task
The data is formatted to the TRMM standard and sent to the ground system.
The purpose of the conversion routine is to filter out and separate the
lightning, background, and platform/instrument health measurements into
separate data streams.
The lightning data stream contains many non-lightning artifacts. The
purpose of this routine is to remove thise pixels.
The purpose of this routine is to convert the TRMM native format
ephemeris into a stream of satellite locations and satellite orientation
vectors.
The purpose of this routine is to identify and remove anomalous artifacts in
the TRMM ephemeris.
Lightning, background, and ephemeris data is combined to produce
lightning and background data projected to Earth coordinates.
This routine computes view times of lightning observation for 0.5 x 0.5
latitude/longitude grids within the field of view of LIS during an orbit.
The routine first clusters the data to the flash level and then uses statistical
information to filter the flash data.
The purpose of this routine is to remove the data due to geolocation errors,
and to remove remained NLE (Non Lightning Event).
In this routine, the accepted flashes are then clustered into areas.
In this routine two kinds of filtering are carried out.
The first is the Putback algorithm that returns previously rejected noise data
to the output stream based on the recalculated noise rates. The second type
removes flashes from the data stream based on their very non-lightning
characteristics.
The final step is to convert the data into HDF and write it to the two HDF
files.
e.
f.
In addition to these six data models, a vgroup is designed to associate related objects.
4-6 5
HDF data models are designed to support only those data elements which are applicable to the
group as a whole. In other words, data models are limited to data elements which make sense in
the context of the group. The 24-bit raster model, for example, will not support palettes or threedimensional arrays because neither of them are necessary for 24-bit imaging operations.
Figure 4.2-2 The Three Levels of Interaction with the HDF File Format
At its lowest level, HDF is a physical file format for storing scientific data. At its highest level,
HDF is a collection of utilities and applications for manipulating, viewing, and analyzing data in
HDF files. Between these levels, HDF is a software library that provides high-level APIs and a
4-6 6
following.
SwathStructure........ A text block which specifies which geolocations and times apply to which
elements of the IFOV data.
Scan Time ............. A Vdata. 8-byte float or several integers whose sizes sum to 8 bytes
Geolocation............ An SDS containing latitude and longitude (4-byte float).
Scan data .............. It applies to the whole scan and can take the form of one or more Vdatas or
SDSs. IFOV data
It occurs at every pixel or at regular pixel intervals
(e.g., every 10 pixels) and takes the form of one or more SDSs.
In that Vgroup appear one GridStructure, one or more Data Grids, and other Data. GridStructure is
a single Vdata which allows the geometric interpretation of the grids. GridStructure is an object
that mimics an attribute, since HDF has not yet defined attributes for Vgroups. This imitation of an
attribute is implemented as a Vdata with the name GridStructure and the class Attr0.0 , one field
named VALUES, number type of DFNT_CHAR8, and order equal to the length of the text. This
specification of GridStructure anticipates the HDF development of attributes for Vgroups. The
maximum expected size for GridStructure is 5000 bytes. Since the purpose of GridStructure is to
allow EOSDIS to ingest data into their archive, Algorithm Developers do not need to read from or
write to GridStructure. Figure 4.2-4 specifies the fields within GridStructure. Six of the fields (the
resolutions and bounding coordinates) are also found in Core Metadata. Three fields (bin_meth,
registration, and Origin) are not found in Core Metadata.
4-7 0
4-7 1
4-7 2
The formats in this document for products with overlap (1A-11, 1B-11, and 2A-12) follow the
assumption that uniformity within one granule is preferable to uniformity for the same pixel across
granules. Therefore one ephemeris file and one UTCF are used in one granule. In a similar vein,
the calibration is started at the beginning of the granule and reaches satisfactory values within
10scans. The advantage of granule uniformity is that there are no discontinuities within a granule
and processing has only to input one granule in order to output one granule. The disadvantage is
that a pixel in one granule may have a different value, location, and time from the same pixel in
another granule. When such a difference occurs, the pixel is in an overlap region in one of the
granules. According to the TRMM requirements, the location and time differences will be less than
1 km and 1 ms, respectively.
In Level-1A, extra (usually one) ACS and instrument housekeeping packets are added to ensure
that each science packet has an ACS and instrument housekeeping packet before and after the
science packet.
Universal Time Correlation Factor (UTCF) derived from the first ACS packet in the orbit. This
UTCF is used to translate the Orbit Start Time from UTC to spacecraft clock time. In normal
processing, the UTCF, the Scan Times in UTC, and the Scan Times in spacecraft clock time are
repeated exactly in Level-1B and higher levels. In the unusual circumstance that the UTCF is
found to be incorrect, a corrected UTCF will be stored in Level-1B and higher data products and a
flag set to indicate that a corrected UTCF was used. When a corrected UTCF is applied, the UTC
Scan Times will be different between (1) Level-1A and (2) Level-1B and higher levels, although
the spacecraft clock Scan Times will be the same in Level-1A and Level-1B and higher levels.
Another flag in Level-1B and higher levels shows whether a leap second occurred in the granule.
Times are expressed in five formats:
(1) UTC times in Core or PS metadata or a Level-1A header are written in three words: Date, Time,
and Milliseconds. For the Begin and End Times in Core metadata, milliseconds is omitted.
Date is a 10 character string with the following characters:
YYYY/MM/DD, where
YYYY = year,
MM = month number,
DD = day of month, and
/ is a literal.
Time is an 8 character string with the following characters:
HH:MM:SS, where
HH = hour,
MM = minute,
SS = second, and
: is a literal.
Milliseconds is a 3 character string with the following characters:
MMM, where
MMM = the number of milliseconds later than the last whole second.
(2) In 1B11 and 2A12, UTC time is stored in separate words for year, month, day of month, hour,
minute, and second.
(3) UTC Scan Time in the body of the data is in seconds of the day. The UTC date and time in the
metadata can be combined with the Scan Time to get a complete date and time for every scan.
4-7 4
(4) Spacecraft clock time and UTCF have the same format.
Spacecraft clock time is the accumulated time count since the power-up of the clock card in the
TRMM Spacecraft Data System onboard the satellite. Spacecraft time is correlated to UTC time by
the UTCF. The sum of the UTCF and Spacecraft time results in a time that represents the total
number of seconds since January 1, 1993 at 00:00:00 (UTC) if one assumes that each day has
exactly 86400 seconds, even days with leap seconds. This total number of seconds allows easy
computation of days since January 1, 1993.
Scan Time is a time associated with each satellite science data scan. It is the time tag written in each
science telemetry packet. There is one scan per science telemetry packet. The relationship of Scan
Time to the time at each IFOV varies by instrument. A description of the relationship between Scan
Time and measurement time for each of the three satellite instruments follows. In each description,
T is the beginning sample time and i is the IFOV number:
(1) For TMI, the equations shown in Table 4.2-2 were obtained by personal communication with
the instrument scientist.
CHANNEL
1,2 (10 GHz)
3,4,5
(19 , 21, GHz)
6, 7 (37 GHz)
8, 9 (85 GHz)
INDICES
i = 1 to 104
i = 1 to 104
SAMPLE
TIME
6.304 ms
6.266 ms
i = 1 to 104
i = 1 to 208
6.304 ms
3.004 ms
(2) For VIRS, the following equation was derived from a viewgraph produced at Hughes and
presented by Bruce Love on January 20, 1995:
T = Scan Time + 107.6 ms + (OFFSET + (i - 1)) * Sample Time,
where i = 1, 261,
Sample Time = 0.29157 ms,
and OFFSET values are shown in Table 4.2-3.
Table 4.2-3 OFFSET Values
CHANNEL
OFFSET
1
0
4
2
5
4
3
6
2
8
4-7 5
The value of Sample Time was derived from the viewgraph using the time of the starting and
ending channel 1 science data as follows:
Sample Time = (183.7 ms - 107.6 ms) / 261
(3) For PR, the following equation is reported.
T = Scan Time + 3.41 ms + (i 1) x 11.768 ms
where i = 1 to 49
4.2.3.8 QAC Error Type
This 1 byte of error information is produced at SDPF only for each packet for which an anomaly is
detected. This byte contains 8 fields, shown if Table 4.2-4, each of which is a flag.
Bit
0
1
2
3
4
5
6
7
4.2.4.1 PR
The following parameters are used in describing format of PR products.
< Level 1 & Level 2 >
- nray
= 49: the number of rays within one PR scan line.
- nscan
= 9150: the number of PR scans within one granule (on average).
- ngeo
= 2: the number of geolocation data.
4-7 6
- ncell1
- mcell2
- nmeth
< Level 3 >
- nlat
- nlon
- nlath
- nlonh
- nh1
- nh2
- nh3
- ncat1
- ncat2
= 80: the number of radar range cells at which the rain rate is estimated.
= 5: the number of radar range cells at which the Z-R parameters are output.
= 2: the number of methods used.
4-7 7
4-7 8
4-7 9
4-8 0
4-8 1
4-8 2
4-8 3
4-8 4
4-8 5
4-8 6
4-8 7
4.2.4.2 TMI
The following parameters are used in describing format of TMI products.
< Level 1 & Level 2 >
- npixel = 208: the number of high resolution pixels within one scan line.
- nscan
= 2991: the number of scans within one granule (on average).
- ngeo
= 2: the number of geolocation data.
- nlayer = 14: the number of profiling layers within one pixel.
< Level 3 >
- nlat
= 16: the number of 5 grid intervals of latitude from 40 N to 40 S .
- nlon
= 72: the number of 5 grid intervals of longitude from 180W to 180E.
(1) 1B11 - Brightness Temperatures
The 1B11 is stored as a Swath Structure in HDF.
4-8 8
Figure 4.2-13 shows the structure of the 1B11 product in terms of the component objects and their
sizes.
4-8 9
4-9 0
4.2.4.3 VIRS
(1) 1B01 - Radiance
The 1B01 is stored as Swath Structure in HDF. The following sizing parameter is used in
describing these formats: nscan = the number of scans within one granule = 18026 (on average).
Figure 4.2-16 shows the structure of the 1B01 product in terms of the component objects and their
sizes. The 1B01 product is stored as a swath structure
4-9 1
4.2.4.4 COMB
(1) 2B31 Rain Profile
The 2B31 is stored as Swath Structure in HDF.
Figure 4.2-17 shows the structure of the 2B31 product in terms of the component objects and their
sizes. The following sizing parameter is used in describing this format:
- nray
= 49: the number of rays within one PR scan line.
- nscan
= 9150: the number of PR scans within one granule (on average).
- ngeo
= 2: the number of geolocation data.
- Nradarrange = 80: the number of radar range gates, up to about 20 km from the earth ellipsoid.
4-9 2
4-9 3
4-9 4
4-9 5
Function
Error Handling
This section provides a brief introduction of TSDIS tool kit routines. The purpose of the tool kits
is twofold, the first being to provide sets of common functions, constants and macros for use by
algorithm developers.
These common items are prepared in the tool kit to reduce the volume of code development being
4-9 6
carried out simultaneously by algorithm developers. This will, for example, reduce to a minimum
the necessity of each algorithm developer codifying their own I/O routines. These routines are
designed so that algorithm developers can easily use them at their research centers. This means that
these routines include basic functions used by the majority of algorithm developers.
The second objective of the tool kits is to allow the simple incorporation of TRMM algorithms into
TSDIS computer environments. As TSDIS treats received algorithms as black boxes, it is
fundamental that interface with TSDIS is defined consistently in the algorithms. In this way tool kit
development concentrates on these routines that are intrinsic in interaction with TSDIS computer
environments.
Tool kit routine categories that have been developed are described in Section 2 of ICS. The
routines are selected from each category, and describe a general outline of how they are used.
This is continued in the same fashion in Section 3 where there are explanations with examples of
how each routine is used. A parameter dictionary is also provided for the calling sequence of
each routine, which defines each parameter. This parameter dictionary is used by algorithm
developers to find out where each parameter is used.
Tool kits routines are codified in line with file specifications in ICS release 2, volume 3 (level 1 file
specifications) and volume 4 ( level 2 and 3 specifications). The current release (release 5.7) of the
TSDIS tool kits is supported by DEC, SGI, Sun and HP computers. The following functions are
included in this release.
In this section, tool kit routine was roughly introduced, and in the following section, the outline of
some tool kits, such as I/O toolkit, Conversion tool kit and Geolocation toolkit, are explained.
The latest status about tool kit is provided from the Toolkit Fast Fact Information on TSDIS
home page (http://www-tsdis.gsfc.nasa.goc/tsdis/tsdistk.html).
4-9 7
been reached.
- Data Access (Scan) : TKreadScan, TKwriteScan
TKreadScan reads a single scan from an opened file containing scan based satellite data.
TKwriteScan writes a single scan to an opened file containing scan based satellite data.
- Data Access (Grid) : TKreadGrid, TKwriteGrid
These routines read and write data for Level 3 grid based satellite data products, and Level 2
and 3 GV products.
- Data Access (L1 GV): TKgetNvos, TKgetNsensor, TKgetNparam, TKgetNcell, TKgetNray,
TKgetNsweep, TKsetL1GVtemplate, TKreadL1GV, TKwriteL1GV,
TKreadL1GVparm,
TKreadL1GVdate,
TKreadL1GVbyVosNum,
TKfreeL1GV
These routines access L1 GV data products. The TKgetNxxx routines provide information
about the granule; TKsetL1GVtemplate creates a template for an output data product; and
TKreadL1GV and TKwriteL1GV read and write the L1 GV data. TKreadL1GVparm will
read a VOS with the specified parameter, TKreadL1GVdate will read all of the start and stop
times of the VOSs in a granule, TKreadL1GVbyVosNum will read a VOS with a user
specified VOS number and TKfreeL1GV will free the memory associated with and user
allocated VOS structure.
- Metadata Access
: TKreadMetadataChar,TKwriteMetadataChar, TKreadMetadataFloat,
TKwriteMetadataFloat,TKreadMetadataInt, TKwriteMetadataInt
There is a separate metadata routine for Character, Floating Point and Integer data types. The
TKreadMetadataTYPE routines read a single metadata element into a typed variable. The
TKwriteMetadataTYPE routine writes a single metadata element to a file. Since the metadata
is stored internally as characters, these routines translate from or to the appropriate type.
- Header Access
TKreadHeader and TKwriteHeader read and write the ray header for PR L1B21 and L1C21
data products, and read and write clutter flags for L2A25 PR data products.
TKcopyScanHeader will copy elements of the swathdata structure from the specified input
granule to the specified output granule.
4-9 8
4-9 9
4.4 OrbitViewer
The orbit viewer is the TRMM data viewer, which is developed by NASA/TSDIS. It is freely
distributed from NASA/TSDIS and NASDA/EORC. The original version of Orbit viewer
separately requires IDL, but currently, the necessary IDL run-time library is combined to the Orbi
viewer. It works without IDL software.
UNIX version, Windows version and Linux version were prepared from the following home page.
TSDIS (URL: http//tisdis.gsfc.nasa.gov/tsdis/)
Original Version (for Unix), Run-time version (for Windows)
EORC (URLhttp//www.eorc.nasda.go.jp/TRMM)
Run-time version (for Unix and Windows)
The Orbit Viewer makes it easy to perform an initial examination of TRMM data files. The viewer
allows you to display TRMM data at the full instrument resolution on a map of the tropics. Vertical
cross sections and 3D images of rain structure can also be created.
4-100
Catalog
Information
Services
General
Users
PI
WWW
GUI
WWW
WWW
GUI
WWW
ADS
ADS
EOIS
Services
for TRMM
Order
Services
Obs Plan
Services
Other
Services
GUI
WWW*
OREQ
OREQ
DRS
DRS
ADS
ADS
5-1
Section 5
Level
1C21
2A25
Description
Radar refraction factor is indicated as color data which is 3 swath and
centered TRMM ground footprint. Horizontal resolution is 10 km x 10 km,
vertical 500 m.
Horizontal profile at 2 km
Horizontal profile at 4 km
Vertical profile at nadir
Indicate rain rate instead of radar refraction factor against above.
5-2
Guide information is a part of image catalog stored in EOC and accessible from the EOC Home
Page.
Table 5.2-3
Sensor
PR
Level
1C21, 2A25 (Partially)
Type of scene
Full-scene/fixed region/sub-scene are selectable
Full-scene only
TMI Full-scene/sub-scene are selectable
Full-scene only
VIRS Full-scene/sub-scene are selectable
COMB Full-scene/sub-scene are selectable
Full-scene only
- Fixed Region Sub-scene: Region over Japan which covers 80
South to 35 degree North Latitude.
- Sub-scene: Lat./Long. 10 degree gridded data
Products
1C21, 2A25
1B21, 2A21, 2A23, 3A25, 3A26
1B11, 2A12
3A11
1B01
2B31
3B31, 3B42, 3B43
to 160 degree East Longitude, and 5 degree
5-3
Section 5
Observation date
Processing level
Name of data set
Type of scene
Scene number
Sub-scene number
Multi file group
Ordering within group
Media
Data code
Product version
Quantity of order
Note
Specify observation date
Specify processing level
Specify data set name
Choose one form full-scene, fixed region*4, sub-scene
Specify sub-scene number when order sub-scene data
Specify group number for multi file
Specify ordering number within the group for multi file
Choose media from 8 mm Tape or CD-ROM
Specify data code*5 of data product
Specify product version (latest version in case of no selection)
Specify quantity of order
Choice
E
E
E
E
E
O*1
O*1
E
E
E
O
E
Note
Beginning date of a providing product
Ending date of a providing product
Specify processing level
Specify data set name
Choose full-scene, fixed region*2, sub-scene
Specify sub-scene number when order sub-scene data
Specify Lat./Lon. Range when order sub-scene data
Choose data unit*3 from 1 day, 10-day, or 1 month
Choose media*4 from 8 mm Tape or CD-ROM
Specify data code*5 of data product
Specify product version (latest version in case of no selection)
Specify quantity of order
E: Essential item requires to be specified, O: Optional item to be specified (For CERES and LIS, no choice except Observation data and
processing level)
*1: Specify for which of range of sub-scene number or lat./lon. range of sub-scene when ordering sub-scene
*2: Choose only when ordering PR 1C21 and/or 2A25
*3: Choose only when ordering PR 2A25 full-scene. For other products, being fixed to month of calendar (10-day or 1 month order is
selectable under a specific contract with NASDA.)
*4: CD-ROM is available only for 1 day product of PR 2A25 full-scene.
*5: Code based on media and data formats
5-4
Satellite
T1
PR
Multi File
Group
Type
of
Scene
Ordering within
Group
Full-scene
Processing Level
1B1C2A3A
21232526
Scene Number
Data Code
Quantity of Order
Fixed region
Sub-scene
MediaCD-ROM8mmOnline
Comments
NASA
Online
Free Users
Archive
NASDA Internal
Users
RESTEC
Order Desk
Level 0 Data
Products
Organizations based
on an agreement
PI, Co-investigators
-EUS
-Order Request
Sheet
Order
Reception
NASDA
Check
Work Order
Data
Processing
Media
Conversion
Shipping
Accounting Users
Distribution Media
EOC
Research Purpose
Users
5-5
Section 5
(1) Products of PR, TMI, VIRS and COMB can be distributed on the same format as that of
master product (no format conversion). It will be produced per each product (sensor,
processing level, type of data set, full-scene/sub-scene.)
(2) CERES, LIS products are deadly copied in the unit of NASA providing products(8 mm tape).
(3) 8 mm tape or CD-ROM is selectable as a distribution.
(4) Generation of products for standing order depends on arrival date of master data and assumes
mass production, so it is pre-scheduled.
(5) The version to be specified by an order, or latest version of master data is adopted for product
generation.
Table 5.3-4
Sensor
Scene Order
8 mm
CD-ROM
PR
OK
OK
TMI
OK
OK
VIRS
OK
OK
COMB
OK
OK
CERES
LIS
Standing Order
8 mm
CD-ROM
OK
OK *
OK
OK
OK
OK
OK
Sensor
Level
PR
1C21
2A25
3A25
Global
3A26
Global
1B11
Sub-scene
2A12
Sub-scene
VIRS
1B01
Sub-scene
COMB
2B31
Sub-scene
TMI
Products
5-6
Figure 5.4-1
5-7
Section 5
Figure 5.4-2
Section 5
5.1.2 EUS/GUI
The EUS/GUI is a software for total online information services that allows PI to utilize a variety
of services in the GUI operation environment offered by the servers in the EOC. Information to get
the EUS/GUI will be provided from the order desk of RESTEC (see Appendix 2).
By selecting the service user wants to use from the EUS/GUI, entering the parameters such as
search criteria, and sending the search request to the servers, user can receive the result of the
search from each server and display it in the appropriate window ( see Figure 5.4-6). Special
permitted users such as PI can send data order through the EUS/GUI.
The current operational software of the EUS/GUI is only EUS/PC Ver. 3.x (Run under Windows
95, Windows 98, Windows NT4.0). When you have EUS/PC Ver. 2.x, it is necessary to update
to the Ver. 3.x.
The EUS/GUI provides the following functions.
(1) Catalog Information Search
Search for standard products catalog information is provided. The following items are available as
the search key : an observation date(period), a pair of latitude and longitude, a data set name, a
satellite name, a sensor name, and other optional search key items.
(2) Image Catalog Data Search
By searching for image catalog data of a standard product, display the image. Use the following
options to display an image.
Zoom in, zoom out, translating display
Enhanced display
Pseudo color display
Bandwidth switching display
Latitude and longitude lines overlay
Multiple data display
Level slicing display
Image position information display
Layer display(Overlay display)
Addition to the options listed above, user can use his own viewer and print image catalogs by
using the customize function later described.
5-10
Catalogue
Subsystem
Browse Data
D istribution
Subsystem
User Request
Ma nage ment
Subsystem
US /GUI
sers (PI)
Ordering Data
Processi ng
*
Film
CT
*
FD
MO
D-ROM
Product
*
8mm
DAT
ASA EOSDIS
Catalog
I nteroperabil ity
Subsyst em
Figure 5.4-6
EOSDIS
IMS Server
Overview of EUS/GUI
5-11
Section 5
5-12
November 28
December 1- 2
December 4
1998
December 8
December 9
December 17
Middle of January
May 22 - June 3
June 1
September 1
1999
May 10 - June 9
November
2000
September 12
November 28
2001
6.1
January 31
A communication line with TDRS was established after fairing cover was opened, and the normal
condition of TRMM satellite was confirmed. And then, TRMM was separated from the H-II launch
vehicle and Solar Array Paddle was deployed, and three axis stabilized attitude was established by
the automatic sequence. After that, the function of TRMM bus instruments and mission instruments
1
Three years extra life is expected based on the remain of fuel of the satellite.
6-1
Section 6
were checked.
The PR was first powered in orbit on December 1, 1997 (JST) and it was confirmed that the radar
was operating normally. After the satellite attained the nominal altitude of 350 km, the PR was set
to the observation mode at 5:45 pm (Japanese standard time) on December 8 to start the initial
check-out. The PR initial check-out, including the performance verification of PR by the ARC, was
completed successfully in middle January, 1998.
PR acquired rainfall data on December 9, 1997 when TRMM passed over Okinawa and over
Cyclone PAM at the northeast of New Zealand. These rainfall data were released as the first
images of PR on December 17. (Figure 6.1-1)
Figure 6-1 (1/2) gives a detailed structure of rain around the cyclone widely and clearly and you can
see there is a rainfall until higher altitude at near the eyewall cloud. PR has the range resolution of
250 m and the horizontal resolution of 4 km and this image shows their performances.
PR is the radar system onboard a satellite. Therefore, PR has an advantage that there is few
difference for ranges separately from ground base radars. In addition, we could observe only
rainfall of close to land area by using radars on ground until now. However, TRMM can observe
them of over sea area. Moreover, usual meteorological satellites can observe only around top of
clouds, on the other hand, PR can measure 3-D structure of rainfall within clouds.
6-2
6-3
Section 6
6-4
6.2
Section 6
Consistency between both data is very well, but with a little deviation. Ground radar of Ishigaki
Island has been technically calibrated and the error of receiving level is within 1 dB.
Figure 6.2-1 Cross Calibration between TRMM PR and Ground Radar at Ishigaki Island
The CAMPR operates at 13.8 GHz that is just the same as the frequency of TRMM PR, and makes
down-looking rainfall observations (similar to TRMM PR). The CAMPR has spatial resolutions
and the sensitivity much higher than those of TRMM PR, and has functions of multi-polarization
and Doppler observations. Therefore, comparisons of TRMM PR and CAMPR data obtained from
simultaneous observations provide a way to validate and evaluate the TRMM PR and its rain
retrieval algorithms. Figure 6.2-2 shows that the CAMPR observation gives higher spatial
resolution and sensitivity, and that you can find a good consistency between them.
Figure 6.2-2
6-6
The synchronous observation of PR and the ground radar was done at the site in Melbourne,
Florida on March 9, 1998. Figure 6.2-3 is the result of synchronous observation, and shows radar
reflectivity distribution at fixed height of 3 km. The both data indicates better consistency on the
radar reflectivity distribution pattern, but the absolute value of PR reflectivity is 2 dB higher than
that of the ground radar. This differential is caused by that the PR sampling volume, size, and
location do not coincide thoroughly with them of the ground radar.
6-7
Section 6
6.3
(1)
Output of 1B21, 1C21, and 2A25
Figure 6.3-1 shows vertical structure of rainfall observed by PR on December 21, 1997 from
Uruguay to northern Argentine. The upper panel is the example of PR 1B21 product, the middle
panel is 1C21 product and the lower panel is 2A25 product. The horizontal axis of each figure
indicates relative Scan Number, which corresponds to distance along TRMM flight direction (1
scan = 4.3 km). The vertical axis of each figure indicates Range Bin Number, which corresponds
to relative distance from satellite (1 Range Bin = 250 m).
PR 1B21 output includes received power. PR 1C21 output includes non-validated radar reflectivity.
PR 2A25 output includes rain rate profile and radar reflectivity that is corrected using rain
attenuation value (lower figure shows rain rate profile). Like this, received power, radar reflectivity,
and rain profile are calculated successively for each normalized radar surface cross section within
IFOV.
(2)
Output of 2A23
Figure 6.3-2 is an example of PR 2A23 product, and it is classified by rain type which include
stratiform, convective and so on. The figure shows observation result of Typhoon No. 28 over sea
in east of Philippines on December 19, 1997. The scene size is 220 km (cross track) x 630 km
(along track).
Figure 6.3-2
(3)
TRMM Level 3 Monthly Rainfall Products
(a)
Output of 3A25
3A25 computes monthly mean rain rate from PR Level 2 data at both a low horizontal resolution (5
x 5 latitude/longitude for near surface and five vertical layers) and a high resolution (0.5 x 0.5
latitude/longitude for near surface and three vertical layers). Note that Figure 6.3-3(2) (low
resolution) and Figure 6.3-3(3) (high resolution) show monthly accumulated rainfall calculated
from original data in order to compare with other Level 3 products.
(b)
Output of 3B31
3B31 uses the high-quality retrievals done for the narrow swath in combined Level 2 (2B31) data
to calibrate the wide swath retrievals generated in TMI Level 2 (2A12) data. It calculates monthly
accumulated rainfall at each 5 x 5 latitude/longitude box for near surface (Figure 6.3-3(4)) and 14
vertical layers. Monthly accumulated rainfall at each 5 x 5 latitude/longitude box for near surface
(Figure 6.3-3(5)) and 14 vertical layers calculated from 2B31 is also included.
(c)
Output of 3B43
(d) 3B43 provides a "best" precipitation estimate in the TRMM region from all global data sources,
namely TRMM, geosynchronous IR, and rain gauges, at each 1 x 1 latitude/longitude box. Note
that Figure 6.3-3(6) shows monthly accumulated rainfall calculated from original data (monthly
mean) in order to compare with other Level 3 products.
6-9
Section 6
Figure 6.3-3
6.4
(1)
Observation Result of El Nino
Figure 6.4-1 shows the global rainfall distribution for January, 1998 (upper panel), and January,
1999 (lower panel), observed by the PR. Differences of rainfall distribution due to El Nino are
clearly seen in these figures. In January, 1998 (upper panel), since El Nino still continued, heavy
rainfall areas in the Pacific shifted from the western to the central Pacific, unlike the normal year.
Due to the effects of El Nino, the inter-tropical convergence zone (ITCZ) was located along the
Equator in the upper panel, and areas of heavy rainfall in the south Pacific shifted further to the east
than in the normal year.
The lower panel shows the rainfall distribution in January of this year, at this time the El Nino
event already finished. Unlike the upper panel, rainfall amount was small in the central equatorial
Pacific and the ITCZ existed in normal location. In addition, large amount of rain was observed in
Indonesia and the center of active convection was observed in its normal location.
Figure 6.4-2 shows the Sea Surface Temperature for El Nino year (January 1998, upper panel),
and Normal year (January 1999, lower panel), observed by the TMI.
6-10
Figure 6.4-2
(2)
Simultaneous Observation by Several Sensors
The images in Figure 6.4-3 are simultaneous images over northern Argentina and Uruguay from
the VIRS, TMI and PR on February 20, 1998. Figure 6.4-3(1) is a color-composite RGB image of
channels 1 (visible), 2 (near infrared) and 4 (infrared) (for red, green and blue respectively)
6-11
Section 6
observed by VIRS. Figure 6.4-3(2) shows the 85 GHz, vertically polarized brightness temperature
observed by TMI. Figure 6.4-3(3) shows the horizontal cross section of rain at 2.0 km height by
PR. Figure 6.4-3(4) shows the vertical cross section rain along the line AB in Figure 6.4-3(3).
Optically thicker cloud at the upper layers are reddish in Figure 1 because of the high reflectivity of
channel 1and their low temperature. Figure 6.4-3(3) shows that rainfall was observed in these areas.
It is clear in Figure 6.4-3(4) that the heavy rain developed in the layer above the heavy rain in the
lower layers. Generally, there were ice crystals over the rain which developed at high altitudes. The
brightness temperature in Figure 6.4-3(2) decreased due to microwave scattering caused by these
ice crystals.
In this way, the rainfall process in the clouds and the characteristics of rainfall will be revealed by
the simultaneous measurement by these three sensors.
TMI and VIRS, usually used for presumption of rainfall, are boarded on TRMM with PR and these
three sensors can acquire rainfall data simultaneously in different way. Before TRMM, it was too
difficult to adjust rainfall measurement results from these sensors. So, it is expected that the data
processing algorithm of each sensors will be improved by using TRMM data.
(3)
Soil Wetness Estimated from PR
Backscattering data from the PR includes not only the information of soil wetness but also
vegetation amount and land surface roughness. Using the information of NDVI from visible and
infrared sensors and the theory of microwave scattering, the effects from vegetation and roughness
were first subtracted, and then soil wetness was estimated. The upper panel of Figure 6.4-4 is the
estimated soil wetness for February 1998 and the lower panel is for August 1998. Comparing the
estimates for February and August, the Amazon River basin in South America is wet in February
during the rainy season and dries up in August, corresponding to the dry season. The Orinoco river
basin, which is adjacent to north of the Amazon, behaves in the opposite manner. Wetting in the
Asian Monsoon region is dominant as well. In the false color composite maps of PR backscattering,
various patterns are recognized in desert areas. However, the Sahara desert and the Rubal Khali
desert are classified as arid regions in these quantitatively estimated soil wetness maps. In some
mountainous areas where the scattering theory of dependency of incident angle cannot be applied
due to the effects of steep slopes and in some tropical rainforest areas where the forest is extremely
dense, soil wetness cannot be estimated by this algorithm. Such regions are shown in black as
missing data areas. The black region in the Northwestern part of Australia indicates missing PR
observation data due to the frequency conflict.
Figure 6.4-4
6-13
Section 6
(4)
Long-wave Top of Atmosphere Flux
Figure 6.4-5 shows the amount of heat energy, which is emitted from the Earth and its atmosphere
and observed by CERES on December 28, 1997. The color scale ranges from cold to hot. Blue
indicates cold tops of cloud systems, and red, hotter regions on the Earth such as the deserts and
tropical oceans.
The anomaly that an over voltage was loaded for the CERES instrument occurred around August
1998, 9 months after launch, analysis of the cause and some counterplans have been performed
until now. Therefore the science data acquisition is limited, intermittently done.
Figure 6.4-5
(5)
Total Number of Lightning Flashes
Figure 6.4-6 shows the total number of lightning flashes, which was observed by LIS in January
1998. Lightning was concentrated over the inland in the Southern Hemisphere (the African
continent, the Australia continent and the South America continent) in January when it was
midsummer in the Southern Hemisphere. Lightning was not observed over the ocean in the
Southern Hemisphere even though it was also midsummer. Lightning over the ocean was observed
like a line only over the equator; these areas correspond to the Inter Tropical Convergence Zone
(ITCZ). Although lightning in the Northern Hemisphere where it was winter, was not so active.
There were some lightning flashes near Japan and the east coast of North America where winter
6-14
lightning is sometimes generated. The winter lightning is "single lightning" because of its weak
activity and short duration. LIS observed this kind of lightning.
6.5
TRMM Follow-On
(1)
Expectation to the TRMM Follow-On Mission
TRMM is launched successfully in November 1997, and it keeps sending data on the threedimensional construction of the rainfall after that, and it is expected a future big scientific result.
However, there is limitation to grasp the rainfall distribution and fluctuation conditions of the world.
Though a rainfall changes even for a short period of time, there is long fluctuation, too. When the
amount of precipitation of the Indian Monsoon for about 100 years is seen, it has known that there
are a few rainfall at the time of the El Nino in an Indian Monsoon area. This El Nino appears
several times during 10 years.
The mission life of TRMM is limited, and it has the possibility that the fluctuation of the cycle of
the El Nino and La Nina can' t be observed only with TRMM. Actually, the El Nino, said as the
century maximum, appeared in 1997, and became a maximum term in December. On the other hand,
it was November 1997 that TRMM was launched, and PR observation was started from December.
Therefore, TRMM couldn' t observe this El Nino in the period when it appeared. As for the El Nino
and the La Nina, which is that opposite phenomenon, magnitude changes every time. Then, some
times of El Nino/La Nina observation is necessary to search for that fluctuation factor. Therefore, a
precipitation observation mission following to TRMM is necessary to get the rainfall distribution
and time fluctuation for longer period.
There is the second peak in the medium latitude area as for the rainfall though there is the biggest
peak of course in the tropical area when it averages the rainfall of the world in the longitude
6-15
Section 6
direction and only latitude distribution is seen. This is a precipitation caused by the low pressure of
the medium latitude. Low pressure like a typhoon appears with Okhotsk Ocean in Japanese winter,
and active cumulus activities are accompanied with it. The observation area of TRMM doesn' t
cover these activities. When the water circulation is grasped globally, it is necessary to do
observation including the peak of the precipitation distribution of the temperate zone and the
subpolar zone. Latent heat emission due to the precipitation activities influence the construction of
the tropical cyclone, and it is necessary for it to know the amount and vertical distribution of nonthermal insulation heating which a precipitation process gives each low pressure.
Therefore, a plan for a TRMM follow-on is discussed continuously as ATMOS-A1 in Japan. And,
the same mission is proposed in the United States. Moreover, the PR of TRMM is the first satellite
loading rainfall observation radar in the world, and many development elements are left as for the
technical side as well. Therefore, a concept for the TRMM follow-on has been planned since a
prospect was made for the realization of the TRMM plan.
A concept for TRMM was planned in the NASA Goddard Space Flight Center in 1986. At that time,
the reliability of the rainfall observation due to the microwave radiometer from the satellite wasn' t
satisfactory yet. On the other hand, it was aware of the significance of the rainfall of the heat band
as a source of drive for the atmosphere circulation, and therefore a PR was made indispensable as a
rainfall sensor boarded on satellite. At present, rainfall observation is made considerably by the
microwave radiometer and the visibility and infrared radiometer as well. These satellite observation
data is combined with the ground rainfall measured value and so on, and the rainfall distribution
map of the world is being made at present.
The purpose of TRMM is a little different under such conditions since that the concept was shown.
At the beginning of mission, it was the major purpose to grasp rainfall distribution with the TRMM.
However, at present, the purpose of PR data usage has been changed variously. For example, PR
data is used to improve the accuracy of rainfall estimation of the other sensors boarded on TRMM,
and also used for the estimation of the latent heat emission professional file. Like this, the PR data
which grasps the three-dimensional construction of the precipitation system, is utilized for the
accuracy improvement of the TMI and VIRS data within the PR observation width of 215 km of the
PR. Furthermore, observation accuracy improves in the TMI and VIRS observation width of more
than 760 km. TRMM data is associated to the rainfall observation data of the other satellites, such
as SSM/I, NOAA, GMS and so on, and this method makes the climate value of the total rainfall
distribution more accurately. This concept for TRMM data utilization is also adopted in the project
of TRMM follow-on.
The backgrounds and the characteristics of TRMM follow-on are shown as follows.
6-16
Three-dimensional rainfall profile can be grasped globally by the observation from radar
onboard satellite.
Three dimensional rainfall profile is very critical information for understanding vertical
distribution of atmospheric heat due to the precipitation activities.
Three-dimensional rainfall profile is very critical information for grasping up-down heat
mixing and aqua circulation due to the precipitation activities.
The precipitation estimation accuracy of microwave radiometer and visible and infrared
radiometer is improved by referring of the rainfall vertical construction observed by satellite
radar.
The visible and infrared radiometer data of SSM/Is, AVHRR and stationary satellite has been
already stored and will be also observed in the future. The precipitation estimation accuracy is
improved for these visible and infrared radiometer data observed by SSM/I, AVHRR and
stationary satellite.
Observation coverage will be extended from Tropical region up to higher latitude region.
Improvement on observation accuracy and sensitivity will be expected by 2-frequency radar.
Classification between precipitation and snow will be realized.
(2)
Outline of the Follow-on Program
(a)
Satellite
The outline of the TRMM follow-on mission is shown in the following. Currently, Japan has
responsibility to develop precipitation radar and launch satellite, and the United States has
responsibility to develop the satellite bus and microwave imager.
Launch Date
: approx. 2007
Design Life Time : 5 years
Satellite Mass
: 2.5 tons class
Orbit Attitude
: approx. 400km
Orbit Inclination : approx. 70 degrees
Sensor
: PR (2 frequencies), Microwave Imager, others
PR: Frequency
: 14/35 GHz
Distance resolution : 250 m
Horizontal resolution : 4 km
Sensibility
: approx. 10 dBZ
Swath Width
: 200 km (14 GHz), 100 km (35 GHz)
6-17
Section 6
6-18
(d)
Plan of the United States (GPM : Global Precipitation Mission)
In the United States, there is a plan to observe precipitation with the time resolution of three hours
by several small satellites of Microwave Imager and 1 core satellite on polar orbit. This plan is
called Global Precipitation Mission (GPM). In this plan, eight small satellites are planned. And, the
TRMM follow-on is placed as the core satellite of this system. The estimated value of the
Microwave Imager can be improved by the observation data of radar of the core satellite. Though
there is a problem that sampling error becomes loud when it tries to observe high latitude as for the
TRMM follow-on, there is an advantage that this problem can be avoided by many small-scale
Microwave Imager satellites.
At present, Japan and US are coordinating to set up a joint project based on concepts of both GPM
and ATOMS-A1.
6-19
DDS
DES
DGS
DMR
DRS
DSN
DSS
ECS
EOC
EOIS
EORC
EOS
EOSDIS
EPV
ERBE
ERBS
EROS
ESA
ESA
ESDIS
ETS
EUS
EVD
FCIF
FD
FDD
FDDI
FDF
FOT
FOV
FTP
GCI
GDPF
GDS
GEO
GEWEX
GMS
GN
GOES
GPCP
GPI
GRS
GSACE
GSFC
GSTDN
GUI
GV
A1-1
HDF
HGA
HGADS
HGAS
HK
HP
HYB
ICS
IFOV
IMS
INT
IOA
IP
IPSDU
IR
IRS
IRU
ISCCP
ISO
JPEG
JFIF
JMA
JPL
L&IOC
LAN
LaRC
LHCP
LIS
LNA
LOGAMP
LVPC
LW
LZP
MAM
MCS
MDSS
METOSAT
MLI
MO&DSD
MOC
MOSDD
MSFC
MTB
N/A
NASA
NASCOM
A1-2
H
: Hierarchical Data Format
: High Gain Antenna
: High Gain Antenna Deployment System
: High Gain Antenna System
: Housekeeping
: Hewlett Packard Co.
: Hybrid
I
: Interface Control Specification
: Instantaneous FOV
: Information Management System (NASA)
: Integration
: Initial Orbit Acquisition
: Internet Protocol
: Instrument Power Switching and
Distribution Unit
: Infrared
: Information Retrieval System
: Inertial Reference Unit
: International Satellite Cloud Climatology
Project
: Isolator
J
: Joint Photographic Coding Experts Group
: JPEG File Interchange Format
: Japan Meteorological Agency
: Jet Propulsion Laboratory
L
: Launch and In-orbit Checkout
: Local Area Network
: Langley Research Center (NASA)
: Left-Hand Circular Polarization
: Lightning Imaging Sensor
: Low Noise Amplifier
: Logarithmic Amplifier
: Low Voltage Power Connector
: Longwave
: Level-0 Processed
M
: Mirror Attenuator Mosaic
: Media Conversion Subsystem
: Master Data Storage System
: Meteorological Satellite
: Multi Layer Insulation
: Mission Operations and Data Systems
Directorate
: Mission Operations Center (NASA)
: Mission Operations and System
Development Division
: Marshall Space Flight Center (NASA)
: Magnetic Torque Bar
N
: Not Applicable
: National Aeronautics and Space
Administration
: NASA Communications Network
NASDA
NCC
NCEP
NCSA
NMS
NOAA
NS
NUBF
OLIS
OSR
OTD
PBIU
PC
PCM
PDB
PGS
PHS
PI
PLO
POD
PR
PRF
PRI
PROP
PS
PS
PS
PSDU
PSE
PSIB
QAC
QL
R&RR
R/T
RAM
RAP
RCS
RDA
REF
REM
RESTEC
RF
RHCP
RIS
ROM
RS
RST
RTEP
RWA
S/C
S/N
SA
SADA
SADDS
SARB
SCDP
SCF
SCID
SDF
SDOC
SDPF
SDS
SFDU
SGI
SH/LP
SMS
SMSS
SN
SNR
SOC
SOCC
SP
SPRU
SSF
SSLG
SSM/I
SSPA
STDN
STR
SW
T/R
TACC
TAM
TCP
TCS
TDA
TDRS
TK
TMI
TOA
TRMM
TRS
TSDIS
TSM
TSU
TX
UPD
UPS
URL
URS
UTC
UTCF
VCID
VIRS
VIS
VSWR
WFF
WGS
WRS
WS
WSC
WWW
XMTR
A1-3
A2-1
Appendix-2
RELATED INFORMATION
A2-2
A2-3
Appendix-2
RELATED INFORMATION
A2-4