# Presentation: 406526

## 3rd International TRMM ConferenceLas Vegas, NV Feb 4 – Feb 8, 2008Erich Franz Stocker, NASA/GSFC Code 610.2John Kwiatkowski, George Mason University, Fairfax VA

## PPS– What and When

**PPS– is essentially Build 1 of Precipitation Processing System (PPS)**
- Includes hybrid production that uses both SGI and Linux
- Does not use PPS toolkit but uses current TSDIS toolkit
- Does not include SOAP services
- Modified to deal with some TSDIS implementation issues (e.g. internal naming, table structure, toolkit interface by algorithm code)
- Uses TSDIS naming conventions
- Still uses GSFC DAAC as archive
**Hybrid**
- PR processing from Level 0 through Level 1C done on the SGI *(until JAXA completes a Linux port of Level 1 algorithm code --scheduled for late 2008)*
- Realtime processing for all instrument continues on the SGI
- TMI and VIRS L0 and L1 processing on Linux
- All instruments L2 through L3 processing on Linux
**Initially planned for changeover on 1 January but testing demonstrated need to automate some additional product error checking and data flow**
**Current conversion target: 1 June 2008**

## PPS– Production Hardware Environment

**Beowulf cluster environment**
- Penguin rack-based hardware
- 64 bit Scyld Beowulf operating system (based on CentOS Linux)
**Production**
- 2 Dual core host nodes, AMD opteron, 8GB memory each
- 1 host active and 1 cold backup
- manages the compute nodes and handles outside network connection
- 96 compute nodes
- Single dual core AMD opteron each 6 GB memory
- No disks (boot from host)
- Everything runs from memory
- Panasas cluster file fast storage (processing buffer): 40TB
- Storage manager server
- Mini-cluster
- Host node with two dual core AMD opteron 8 GB memory
- 8 compute nodes with extra 1 GB network card
- Manage 800 TB of RAID 6 SATA. Permanent archive storage
- gcc C compiler and Intel Fortran 77/90 compiler

## PPS– ITE Hardware

**Integration and Test Environment**
- Used for testing and integrating new or updated science algorithm code
- Debugging
- Initial multi-month test of new or updated algorithms
**Beowulf clustered hardware**
**Set up similar to the production cluster so a valid testing platform**
**Hardware**
- 1 host node with two dual core AMD opterons, 8GB of memory
- 32 compute nodes
- Single core AMD opteron, 6 GB of memory
- Diskless, booting from host
- All processing done in memory
- Panasas clustered file fast storage (processing buffer): 20 TB
- Access to the TRMM long-term archive

## PPS-- Changes

**Difference in hardware architecture, particularly change to 64 bit, creates some ****scientifically insignificant**** differences in product values:  **_**See John Kwiatkowski poster**_
**Satellite browse is by orbit and stored in PNG format. **
- In TSDIS satellite browse was daily
- In TSDIS browse in HDF and required special browser
**Satellite coincidence products calculated using rectangle around coincident site rather than center point and radius of the site.**
**GV data just a pass through to the DAAC**
**No coincident products produced from the GV datasets**
**GV browse is by hour and stored in PNG format**
**RST disappears as we have online access to TRMM data for TSU**

## Additional PPS-- Services

**Science Team Online Request Module (STORM) provides the query/request access to TRMM data**
**Because satellite browse is in PNG the STORM interface can display as part of data selection process**
**All members of Precipitation Measurement Missions (PMM) science team may get accounts **
- TSDIS allowed just algorithm code developers and scientists involved with validation of satellite algorithms
- PPS– will also give accounts to grad students, post-Docs, etc. working with science team members on their funded topic
- More liberal extension of accounts to other precipitation scientists
**Anyone has query access via STORM to the TRMM database and through STORM to the online archive**
**Direct access in the webpage to the online archive**
**Users with accounts can:**
- Get special request geographical subsets created and subset products put in their accounts. Users notified via email upon subset product creation
- Establish standing orders that are based on geographical areas of interest
**STORM access to TRMM trending products (services page on next slide)**

## STORM Science User Services Page

## Online Access to TRMM Data

**All TRMM data is currently available online and this will continue via PPS—**
**Anonymous ftp: trmmopen.gsfc.nasa.gov *****(your email is password)***
**Currently only a single version (Version 6) is available. **
- When V7 reprocessing starts, PPS– will maintain V6 and V7
- Generally, current version and previous version will be available online
**Two paths to the TRMM data**
- By instrument
- By date
**By Instrument**
- pub/trmmdata/ByInstrument/V06/*INST*/YYYY/MM/DD
*INST* may be Browse,PRC,TMI,TO,VIRS
- YYYY, 4 digit year; MM, 2 digit month; DD, 2 digit day
- All files for that instrument category available at the day level

## Online Access to TRMM Data (2)

**ByDate**
- pub/trmmdata/ByDate/V06/YYYY/MM/DD
- YYYY, 4 digit year; MM, 2 digit month; DD, 2 digit day
- All TRMM data product files regardless of instrument available at the day level
**Regardless of where the data actually resides, users or user automated scripts can DEPEND upon access through these 2 paths**

## Streamlined TRMM Near-realtime Access

**Access approval for TRMM near-realtime granted by TRMM Data Manager and TRMM Project Scientist**
- Send email to _[Erich.F.Stocker@nasa.gov](mailto:Erich.F.Stocker@nasa.gov)_
- Include: name,`address, telephone number, email
- Provide reason for access: operations, research, etc  {kept for information}
- Provide additional contacts to be notified when maintenance or issues cause downtime of  near-realtime
**Upon reception, users will be sent the necessary access information via email**
- Still uses user account and password
- Password generally changed every 120 days (keep in mind when setting up scripts)
- Valid email necessary for access so realtime status, password change, and other key information can be sent to users.
**Turnaround time generally with 24 hours of receiving a complete email request**
**HQ Program Scientist will be informed of all new users of the TRMM near realtime data**