Decoding ATOVS Data

After an HRPT, GAC, or LAC pass finishes, the POES ingestor sends an e-mail event to all users in the event notifier list file, /data/notify.list. The user klmtip should be in/data/notify.list. The user klmtip is a mail alias that starts a script called /opt/tip/bin/klm_tip. This script reads the appropriate configuration files, and calls other scripts and programs to produce the final ATOVS areas. ATOVS areas are put into /home/tip. The Level 1b files are put into /data/l1b.

The first thing done by the klm_tip script is to read the configuration file /home/tip/.tiprc. This file sets up the environment and other defaults for the script. The klm_tip script reads the appropriate configuration file named noaa<sat#>_<noaaid#>_tip.cfg (e.g., noaa17_11_tip.cfg). This configuration file has information about whether the file is to be decoded or not, and area ranges. The script klm_tip then runs the program /opt/tip/bin/l1b on the image referred to in the mail event message. This program creates three Level 1b files: a HIRS/3 file, an AMSU-A file, and an AMSU-B file. If areas are also to be generated, three more programs are run: amsua, amsub, and hirs. These programs create the areas and place them in the directory /home/tip.

The diagram below describes the flow of data to produce decoded ATOVS data.

Flow of data to produce decoded TOVS data

[Search Manual] [Table of Contents] [FAQ] [Go to Previous] [Go to Next]