2  SYSTEM DESCRIPTION

This section provides a description of the overall ATCF system, the files used and produced, and the scripts and executables used to implement the system. It is intended to provide background information that will serve as a basis for the sections that follow.

2.1  The atcfEnvs File

Much of the discussion below hinges on an understanding of the ATCF file and directory structure. The “road map” for an ATCF installation is contained in the atcfEnvs file that sets the environment variables for that installation. The actual locations of directories and files will vary from installation to installation, so ATCF uses the environment variables rather than the actual filenames in order to be consistent across all installations. So when ATCF wants to access the Storms directory, for example, it uses $ATCFSTRMS rather than the actual directory path. It is therefore imperative that each installation tailor the atcfEnvs file to match its own environment. A sample atcfEnvs file is provided below for reference.

#----------------------------------------------------------------------------------
#
# PURPOSE: ATCF System C-Shell Environment
#
# DESCRIPTION:
# Set Env variables that are used by the ATCF system and other various
# components of the ATCF to ensure a fully functioning system.
#
# USAGE:
# call this env setup inside $HOME/.cshrc or $HOME
#
# RESTRICTIONS:
# Only authorized ATCF System Adminsitrators should set these env variables
#
# MODIFICATION HISTORY:
# 28-Feb-2008 CAS - refactored environment systems for easier usage
#
#----------------------------------------------------------------------------------

#-------------------------------------------------------------
#... USER DEFINED "System-Related" ENV VARIABLES (user set)...
#-------------------------------------------------------------

#  main ATCF directory
setenv ATCF /users/atcfcm/atcf

# This user should be of the format site_computer (e.g, nhc_agw)
setenv ATCFUSER nrl_monterey

#-- Site Functionality (used in controls/messaging) --
# User -> (CPHC)
#...setenv ATCFSITE cphc
#  User -> (HPC)
#...setenv ATCFSITE hpc
#  User -> (NHC)
#setenv ATCFSITE nhc
# User -> (NRL)
setenv ATCFSITE jtwc

#Switch to turn on/off mail to NRL TC Web Page
setenv ATCFSENDMAIL 0

#-------------------------------------------------------------
#... USER DEFINED "Data-Related" ENV VARIABLES (user set)...
#-------------------------------------------------------------

# Temporary scratch space
setenv ATCFTMP $ATCF/tmp

# Turnover directory for watch relief
setenv ATCFSHARE $ATCF/turnover

# directory for "send to lan" function
#setenv ATCFLAN /home/dpsr/J100
setenv ATCFLAN /tmp

#  satellite and radar imagery (jif images)
setenv ATCFSATIMAGES $ATCF/images

# Output file directory, runfiles, debugging
setenv ATCFOUTPUT $ATCF/output

#-----------------------------------------------------
#... STATIC ATCF SYSTEM ENV VARIABLES (do not set) ...
#-----------------------------------------------------

#  executables
setenv ATCFFLS $ATCF/atcffls

# scripts directory
setenv ATCFSCRIPTS $ATCF/scripts

# configuration files
setenv ATCFINC $ATCF/include

#  standalone programs
setenv STANDALONE $ATCF/standalone

#---------------------------------------------------
#... STATIC ATCF DATA ENV VARIABLES (do not set) ...
#---------------------------------------------------

#  storm files
setenv ATCFSTRMS $ATCF/storms

# storm data archive
setenv
ATCFARCHIVES $ATCF/archives>

# grib file
setenv ATCFGRIB $ATCF/grib

# logos and thumbnail images
setenv
ATCFIMAGES $ATCF/logos

# NHC strike probability data
setenv ATCFPROBLTY $ATCFINC/problty_dat

# wind probability charts
setenv ATCFWINDPROB $ATCF/windprob

# wind probability charts (archives)
setenv ATCFWINDPROBARCHIVES $ATCFWINDPROB/archives

# Generic messages (warnings, ...)
setenv ATCFMESSAGES $ATCF/messages

# NHC messages (advisories, etc)
setenv NHCMESSAGES $ATCF/nhc_messages

# NHC messages archive
setenv NHCMSGARCHIVE $ATCF/nhc_messages/archive

# Processed objective aid messages from outside agencies
setenv ATCFAIDMESSAGES $ATCF/aidmessages

# Processed fix messages from outside agencies
setenv ATCFFIXMESSAGES $ATCF/fixmessages

# Log files for individual storms
setenv ATCFLOG $ATCF/log

# SHIPS directory
setenv ATCFSHIPS $ATCF/ships

# WBAR directory
setenv ATCFWBAR $ATCF/standalone/wbar

# PEST directory
setenv ATCFPEST $ATCF/standalone/PEST

# MRCL - McCadie wind radii cliper directory
setenv ATCFMRCL $ATCF/standalone/MRCL

# Input directory for objective aid data from outside agency (FNMOC)
setenv ATCFFNMOCIN  $ATCF/fnmocin

# Input directory for any fix/aid data from outside ATCF
setenv ATCFINPUT  $ATCF/fnmocin

# Output directory for bogus message
setenv ATCFFNMOCOUT $ATCF/fnmocout

#-----------------------------------------
#... MISC ENV VARIABLES 
#-----------------------------------------

# General utilities, shareware
setenv ATCFBIN /usr/nrl/bin

#Site to post/pick up data
setenv ATCFFTP atcfm1.nmm.nrlmry.navy.mil

# Navy graphic and warning posted to this computer
#setenv ATCFWEBSITE 198.97.95.26
setenv ATCFWEBSITE ftp.nrlmry.navy.mil

# Navy graphic and warning posted to this directory
setenv ATCFWEBDIR receive/sampson/atcf

# Automated gifs generated, sent to this directory
setenv ATCFWEBDIRFIELDS receive/sampson

# Directory for all of the warning graphic files
setenv ATCFWATCH $ATCF/watch

# TC Webpage data are posted to this computer 
setenv ATCFLOCALFTPSITE ftp.nrlmry.navy.mil

# TC Webpage data are posted to this directory
setenv ATCFLOCALFTPDIR  receive/sampson

# Bogus data are posted to this directory
setenv ATCFLOCALBOGDIR  receive/sampson

# NHC computer at NCEP
setenv NHCCOMPUTER prodsp.ncep.noaa.gov

#  Local model data for STIPS, BAMS and WBAR
setenv ATCFLOCALMODELDATA $ATCF/local_model_data
setenv HOME_STORMS $ATCFLOCALMODELDATA

#  New frost database
setenv ATCF_FROST_DB  $ATCF/frostdb
setenv GRIB_ACCEPT_LIST   $ATCF_FROST_DB/GribData/acceptList.txt
setenv ATCF_GRIB_METADATA  $ATCF_FROST_DB/GribData/metaData.txt
setenv ATCF_GRIB_DATASTORE $ATCF_FROST_DB/GribData/dataStore
#setenv MEL_BUFR_TABLES $ATCF_FROST_DB/BufrData/MEL_BUFR/BV_5.3.1/MEL_BUFR_TABLES
setenv ATCF_GRIB_INCOMING  $ATCF_FROST_DB/GribData/incoming
setenv ATCF_OBS_DATASTORE  $ATCF_FROST_DB/BufrData/dataStore
setenv ATCF_OBS_CURRENT    $ATCF_OBS_DATASTORE/current

#---------------------------------------
#... MISC ENV VARIABLES (Deprecated) ...
#---------------------------------------

# Server for gridded data (deprecated)
setenv SERVER omar.nmm.nrlmry.navy.mil
# dcs transmission directory (deprecated)
setenv ATCFSEND /tmp
# dcs transmission directory for satellite page
#setenv ATCFSENDGRAPHIC /home/dpsr/FNOS (deprecated?)
# floppy disk (deprecated)
setenv ATCFFLOPPY /tmp
# ftp site where you can pick up data (deprecated)
setenv ATCFOTHERSITE atcfm1.nmm.nrlmry.navy.mil
#  TAPT directory (deprecated)
setenv ATCF_TAPT $ATCF/jtwc_code/tapt_dir

#-----------------------------------------------------
#... Web-ATCF ENV VARIABLES ...
#-----------------------------------------------------

# executables
setenv ATCFFLS_DSI $ATCF/atcffls_dsi
setenv ATCF_DSI_OBJS $ATCF/atcf_dsi_objs

#---------------------------------------------------
#... Other misc. stuff that probably should go.  ajs
#---------------------------------------------------

# Set time zone
#unsetenv TZ
#setenv TZ GMT0GMT
#
# XVT stuff (in .cshrc)
#
#setenv XVT_DSC_DIR /usr/nrl/xvtdsc50/xm20_pc_linux
# X11 directory
#setenv MOTIFHOME   /usr/X11R6
# XVT path for print function?
#setenv XVTPATH /usr/nrl/xvtdsc50/xm20_pc_linux/print
# XVT path for uids?
#setenv UIDPATH ./%U:~/%U:$ATCF/%U:$ATCFFLS/%U:/usr/nrl/xvtdsc50/xm20_pc_linux/bin/%U:$XVT_DSC_DIR/bin/%U
# XVT path for shared libaries
#setenv LD_LIBRARY_PATH /usr/nrl/xvtdsc50/xm20_pc_linux/lib

#----------------------------------------------------
#... DATA INIT (initialize upon shell invocation) ...
#----------------------------------------------------

# For new atcf installations, create a storms.txt if one doesn't exist.
touch $ATCFSTRMS/storms.txt

2.2  ATCF Data

This section briefly discusses the data used by ATCF. Individual data types will be covered in more detail in Sections 5 and 6. Note that some types of data may be either generated internally or generated externally and then imported or ingested into ATCF.

2.2.1  Externally-Generated Data

These data are generated outside ATCF and stored as flat files in various directories in the ATCF structure, or in a separate flat-file database called fasDB. Table 1 below shows these inputs, the filenames used for each type, the scripts or programs used to ingest them into the ATCF structure, and where they reside within that structure. These data are normally generated by FNMOC and/or National Hurricane Center (NHC).

Table 1. Externally Generated Data

In the table above, the bbnnyyyy portion (called the stormid) of the filename breaks down as follows:

bb Basin identifier. Possible values are:

al    North Atlantic
sl    South Atlantic
ep    Eastern North Pacific
io    Indian Ocean
sh    Southern hemisphere
wp    Western North Pacific
cp    Central North Pacific

nn    Storm number (01-99) within the basin

yyyy    Storm year

Objective aids data (abbnnyyy file) is commonly referred to as the “a-deck” for a storm. Best track data (bbbnnyyy files) is commonly referred to as the “b-deck”. Fix data (fbbnnyyy files) is known as the “f-deck”.

2.2.1.1  Externally-Generated Fix Data

Externally-generated fixes are initially received into the $ATCFINPUT directory. The filenames of the fix files are generally of the format ORG_Type_yyyymmddhhmm_ccb_FIX, where

ORG is the code for the originating organization (e.g. TAFB, SAB, KGWC, CIRA, CIMSS, NHC, NRL)

Type is the code for the type of fix. Fix types include:

DVTS    Dvorak Subjective
DVTO    Dvorak Objective
SSMI    Special Sensor Microwave Imager
QSCT    QuickSCAT
SEAW    SeaWinds Scatterometer
TRMI    TRMM microwave and vis/ir imager
ALTG    Geosat altimeter
AMSU    Advanced microwave sounding unit
RDRC    Conventional radar
RDRD    Doppler radar
RDRT    TRMM radar
SYNP    Synoptic
AIRC    Aircraft
ANAL    Analysis
DRPS    Dropsonde

yyyymmddhhmm is the year, month, day, hour, and minute of the fix.

cc is the storm number.

b is the basin (L = Atlantic, Q = South Atlantic, E = Eastern Pacific, W = Western Pacific, C = Central Pacific, S = Southern Hemisphere, P = Persian Gulf, A = Arabian Sea, B = Bay of Bengal)

One fix file that does not conform with the above format is a microwave fix file from NOAA whose name is of the form <stormid>_yyyymmddhh_NOAA1[568].AFX.

A script called importfixes is run to import selected digital fix data files and merge valid fixes into a storm’s f-deck. Its calling sequence is $ATCFSCRIPTS/importfixes stormid type, where type is one of the types listed above, or ALL to ingest all types of fixes. The output is a new f-deck in the $ATCFSTRMS directory.

2.2.1.2  Externally-Generated Objective Aids Data

Externally-generated objective aids data are received in the $ATCFFNMOCIN directory. The mrgfnmoc script merges newly-received aids into the a-deck for the storm, and moves the individual aids messages into the $STOREMESGDIR directory following the merge.

2.2.1.3  Observations and Gridded Data

The fasdb database, although technically a stand-alone flat-file database, is used by ATCF to store observations and gridded data such as model outputs from FNMOC. Separate documentation for fasdb is referenced in Section 8. This documentation describes how data are ingested into fasdb, how they are stored, and the APIs used to access fasdb data.

2.2.2  Internally-Generated Data

The data shown in Table 2 below are generated internally through entries in the ATCF dialogs.

Table 2. Internally-Generated Data

Probability data (ebbnnyyyy) is referred to as the “e-deck” for a storm.

2.2.3  “Deck” File Structures

The “a-deck”, “b-deck”, “e-deck”, and “f-deck are key files within ATCF. Because these structures are somewhat subject to change, the user is directed to the following online documentation, which will always provide the most up to date information:

2.3  $ATCFSTRMS and $ATCFARCHIVES

There are two data repositories that the system administrator must be particularly aware of. The $ATCFSTRMS directory contains temporary or live data. $ATCFARCHIVES is a permanent repository of storm information.

When a storm is started by the operator, the storm’s data are stored in both $ATCFSTRMS and $ATCFARCHIVES. The data stored include the a-, b-, f-, and e-decks for the storm. When these data are added, index files called storms.txt (in the $ATCFSTRMS directory) and storm.table (in the $ATCFARCHIVES directory) are updated. When the storm is de-activated and deleted and the cleanup function is subsequently performed on the storm directory, the storm’s data is removed from the $ATCFSTRMS directory but remains in the $ATCFARCHIVES directory. The storms.txt file is updated when this occurs. Certain functions (e.g. the statistics functions) used for after-action reporting will “pop” a copy of a de-activated storm’s data from $ATCFARCHIVES back into the $ATCFSTRMS directory temporarily. Again, this causes the storms.txt file to be updated.

To summarize:

• $ATCFSTRMS is a temporary repository of storm data that is actively in use, whether because the storm is still active or because post-processing is being done on it. The storms.txt file maintains an index of storm data currently stored in this directory and is updated whenever data are removed or re-activated.

• $ATCFARCHIVES is a permanent repository of storm data, containing both active and past storms. Within $ATCFARCHIVES, data are stored by storm year. The storm.table index file maintains an index of all storm data stored in $ATCFARCHIVES.

• Newly entered/imported storm data are stored in both $ATCFSTRMS and $ATCFARCHIVES. When a storm is de-activated, its data are removed from $ATCFSTRMS when the storm directory cleanup function is activated, but the data remain in $ATCFARCHIVES. Certain functions can “pop” a copy of data from $ATCFARCHIVES back into $ATCFSTRMS.

2.4  ATCF Workflow

JTWC ESOP 02 provides a progression of tasks for using ATCF to perform routine tropical cyclone forecasting tasks during a watch cycle, but the workflow is dependent on the basin, presence/absence of TCs, development level of TCs, and location of those TCs. The following gives some basic steps for work flow:

1. Start ATCF.

2. Display field data for streamline charts. The data are retrieved from the fasDB database, which in turn is fed by FNMOC’s Come And Get It Product Services (CAGIPS) system. Basically, field retrieval from FNMOC is automated through CAGIPS and the fasDB ingesters.

3. Display and print large Area of Responsibility (AOR) charts for streamline analysis.

4. Start a storm (if required).

5. Open a storm window for an existing storm (if required to update).

6. View satellite/microwave imagery. Satellite images are retrieved by the get_imagery script in $ATCFSCRIPTS, which performs a wget from NRL and FNMOC TC pages. The images are stored in $ATCFIMAGES/<stormid>.

7. Remove imagery (once finished viewing; helps to clean up the display for forecasting tasks).

8. Enter fixes.

9. Make fix labels.

10. Edit fix data (if necessary).

11. Re-Best Track.

12. Create a bogus (not required for weaker systems)

13. Run objective aids for each invest or TC

14. De-activate a storm (for non-invests that no longer require tracking).

15. Delete a storm (for invests that no longer require tracking). This deletes the storm data from $ATCFSTRMS and modifies entries in the index files ($ATCFSTRMS/storms.txt and $ATCFARCHIVES/storm.table) accordingly.

16. Forecast track, intensity, wind radii (if necessary)

17. Generate warning products (if necessary)

2.5  ATCF Products

ATCF is capable of producing a range of products; some of these (e.g. bogus, wind probability text product) are common among sites and others are site-specific (warning, advisory, TCFA). The table below summarizes the common products available and where they are typically distributed.

Table 3. ATCF Products

Other products (e.g. TCFAs, 5-day objective aids graphic, warning graphics) are typically site-specific and posted at the site’s home page or used internally only.