AvnFPS3.2 FAQs and Troubleshooting Web Page

Aviation Forecast Preparation System 3.2
Frequently Asked Questions
(Last Update: 1 December 2006)

[Return to AvnFPS Release Matrix] [Return to AvnFPS3.2 Web Page]

AvnFPS3.2 FAQs

Installation

Q1.1 How long does it take to install AvnFPS3.2?

From the time the "installAVNFPS.sh" command is issued to the time forecasters can start using AvnFPS3.2, is less than10 minutes, barring any difficulties.

[Return to Top] [<<][>>]

Setup

Q2.1   I have a lot of primary and backup TAFs and TWBs. Do I have to redo these for AvnFPS3.2?

No. Your configuration files are untouched. However, AvnFPS3.2 seems to be less tolerant of missing data in the TAF and TWEB configuration files.   Missing data could cause one or more data ingest threads to fail. The ITO and/or the Aviation Focal Point should verify that all required text fields are filled in, i.e., "no pink backgrounds."

[Return to Top]    [<][>]   [<<][>>]

Q2.2 How to get the Aviation Weather Center's Collaborative Convective Forecast Product?

First thing is to make triggers for the new products in your text database, see here to create them. Second, you will need to update some fxa configuration files.

On dx1 edit the file /awips/fxa/data/localizationDataSets/CCC/ispan_table.dat. CCC is your WFO ID and add the following lines:

FAUS27KKCI MKCCFP01
FAUS28KKCI MKCCFP02
FAUS29KKCI MKCCFP03

Add these three lines to /data/fxa/nationalData/ispan_table.template as well.

You'll want to repeat these edits on the dx2 machine as well.

Finally restart FXA data ingest on dx1 for these changes to take effect.

[Return to Top] [<][>] [<<][>>]

Q2.3   We'd like to start issuing 30-h TAFs for one of our airports. How do we do that?

The 30-h TAF consist of two products actually, the original TAF product, 24 hours in length, and a 6-h TAF forecast product for the 24 to 30 hour timeframe issued under a separate PIL and WMO identifier. This extended 6-h forecast product is not amendable.

To begin issuing extended TAF, go the the AvnFPS configuration GUI and start the "Taf Site Info" GUI.   Under the XTF Header field, the WMO ID for extended TAF product is FTUS99 CCCC where the CCCC is your office four-letter identifier. The AFOS PIL is CCCXFTXXX. Press 'Save' to write your changes to the disk, and then exit this GUI. Now press the 'Triggers" button to start that GUI. The display will have the XTF column with the new airport you've just added. Go ahead and add the AFOS PIL in the text field, then press 'Make' to write the new trigger to the text database. The 'Trigger' GUI and AvnSetup GUIs can then be closed. Finally update the afos2awips.txt file to include the AFOS PIL and WMO ID of the new TAF product on machines px1 and px2.

Either bring up a new AvnWatch GUI or restart it to begin issuing 30-h TAFs.

[Return to Top]    [<][>]   [<<][>>]

Q2.4 Where can we download the climate files for the new tools?

The HDF5 files needed for the new climatology tools can be found here. You should put the files, as is, into the


/data/adapt/avnfps/climate

directory, no uncompression or untarring of files required for these datasets. They are ready for immediate use. If you have a location for which you require climatological data and its not available, contact MDL via the avnfps listserver. If the site's observations exist in the NCDC archives, we'll create the HDF5 file(s) and post on our site and let you know of its availability.

[Return to Top] [<][>] [<<][>>]

Q2.5 What about the old climate files? Can they be removed now?

It's the classic answer: "It depends." The first generation conditional climatology tool still exists in AvnFPS3.2 (click on the climate button in the AvnWatch GUI), so if you still want to use that tool you should keep the old climate files around. These are the files in


/data/adapt/avnfps/climate

directory that do not have any file extensions. You should keep the monthly climate digest files--those with the ##.nc extension--as they are needed for the Climate QC functionality in the TAF Editor, so don't remove those.

By the way, the old conditional climatology tool will be removed in OB8.1. At that time, if you haven't done it already, you can remove the old climate files then.

[Return to Top] [<][>] [<<][>>]

Q2.6 How to view climatology from other locations other than my TAF sites?

Download the HDF5 files for the sites you want to see into the


/data/adapt/avnfps/climate

directory. Now using the AvnFPS Text Editor (or any other editor of your choosing, xemacs comes to mind) open the


/awips/adapt/avnfps/etc/ids.cfg

file for editing. You will find for each location, denoted by the identifier surrounded by two brackets, has two attributes: file and pil. file value is the directory path to where to find the HDF5 file for that location. pil is the AFOS identifier for the METAR you what to use for that location when using the Ceiling/Visibility Trend Tool. Just add additional locations to the bottom of this file. Save your changes. Start any of the new climate tools. Your new sites you've added should appear in the 'Site' window.

[Return to Top] [<][>] [<<][>>]

AvnWatch Features

[Return to Top] [<][>] [<<][>>]

Q3.1 How do I rearrange the guidance tabs in the TAF Editor/View? I like to put GFS-MOS first, for instance.

Just about everything in the TAF Editor/Viewer is configurable. Some aspects of the GUI are customizable by the individual, like the use of fonts and size of text windows, but others can only be done via a configuration file. If you want to change layouts, like the tabs in the TAF viewer, you will have to coordinate these changes with your staff as this is done via the gui.cfg file. For the guidance tabs in the viewer, use the AvnFPS text editor (or your favorite editor and go to the /awips/adapt/avnfps/etc directory) and open a file called "gui.cfg"
In there, you will find a section labeled "[viewers]", like this:

# viewers: taf and metar must be present, taf must be first on the list
[viewers]
tags=taf,metar,allmetar,avnmos,ngmmos,gfsmos,etamos,etabuf,grids

The token ordering of the list for "tags" is how the tabs are arranged in the TAF viewer. So if you want GFS-MOS to the first MOS guidance tab from the left (note the restriction: taf token must be first in the list), a change like this will work

tags=taf,gfsmos,ngmmos,avnmos,etamos,etabuf,grids,metar,allmetar

Save the file. This does not require that AvnFPS processes be stopped, just the AvnWatch GUI. Under File, there is a "Restart" option, select that and your changes to gui.cfg will take effect.

See this link for more details on this and other configuration files in AvnFPS3.2.

[Return to Top] [<][>] [<<][>>]

Q3.2 How do I remove guidance tabs like Eta or AVN-MOS from the TAF viewer?

See Q3.1 and, instead of rearranging them, remove tokens from the "tags" list. For BUFR Eta, it corresponds to "etabuf" token, likewise, AVN-MOS corresponds to "avnmos", etc.

[Return to Top] [<][>] [<<][>>]

Q3.3 The LLWS monitoring icon is always grey for my TAF sites. What does that mean?

Your aviation focal point has not turned on LLWS monitoring. Talk to your aviation focal point about providing LLWS monitoring for a TAF site. See this link for more details. Changes to the TAF configuration file, such as turning on (or off) LLWS monitoring, requires that the AvnFPS servers be stopped and restarted for changes to take effect.

[Return to Top] [<][>] [<<][>>]

Q3.4 How do I remove obsolete guidance buttons in the Weather Plot GUI?

To change the guidance buttons in the weather plot GUI, use the AvnFPS text editor (or your favorite editor and go to the /awips/adapt/avnfps/etc directory) and open a file called "wxplot.cfg". In there, you will find a section labeled "[viewers]", like so:

[viewers]
tags=taf,metar,avnmos,gfsmos,etamos,etabuf,grids

Delete the guidance source tag you wish to remove from the GUI. AVNMOS guidance was discontinued on 15th August 2006.
[Return to Top] [<][>] [<<][>>]

Q3.5 How do I get the weather plot GUI to print directly to the printer?

For the guidance button in the weather plot GUI, use the AvnFPS text editor (or your favorite editor and go to the /awips/adapt/avnfps/etc directory) and open a file called "wxplot.cfg"
In there, you will find a section labeled "[print]", like so:

[print]
cmd=convert - tmp/%s.jpg

You should alter the cmd tag to the following

[print]
cmd=convert - -resize 600x1100 jpg:- | lpr -o landscape

This will send the image directly to the printer. The convert program has lots of options so you may want to explore those in more detail. What I've found is that the "jpg:-" token *has* to be the last one to the convert command, or it won't work.

[Return to Top] [<][>] [<<][>>]

Q3.6

Reserved

[Return to Top] [<][>] [<<][>>]

Trouble Shooting

The initial installation and setup of AvnFPS3.2 has its own unique "bumps", "hiccups" and "exploding landmines" and will be addressed here on this FAQ page. However, once you have AvnFPS3.2 up and running routinely, you should consult the AvnFPS User's Guide Trouble Shooting section for more information should problems arise later.

Q4.1 We experienced px1 (or px2) failover (or failback), and the server icons on the AvnWatch GUI are red.

This means that the AvnFPS3.2 servers were not automatically restarted. If you cannot be user "fxa" or cannot find someone at your office who can, call the NCF and tell them you need the AvnFPS servers restarted. The command to do this is:

/awips/adapt/avnfps/bin/remoteServers.sh restart

The NCF engineers have recieved training on AvnFPS, so they should be familiar with the software and have no difficulties restarting the servers.

[Return to Top] [<][>] [<<][>>]

Q4.2 The AvnFPS server icons are green but we aren't getting any new metars (or other real-time text data).

AvnFPS gets its METAR, TAF and TWB text products from the Postgres database via triggers as implemented in the fxatext database's watchwarn table. If you know that your data feeds from your communications processor (cpsbn1 or cpsbn2 machine) are okay and can call up these products using the textdb command, then its likely the trigger entries in the watchwarn table have been removed. See the AvnFPS User's Guide "Creating Database Triggers" on how to re-create them, here. After you've re-created them and if the textdb command fetches current, up-to-date metars, tafs, twbs, etc., then you can manually update AvnFPS by using the avntrigger command:

% /awips/adapt/avnfps/bin/avntrigger CCCNNNXXX

[Return to Top] [<][>] [<<][>>]

Q4.3

Reserved

[Return to Top] [<][>] [<<][>>]

Other Questions

This section is devoted to questions that aren't addressed above or in the AvnFPS User's Guide.

Q5.1 How to add a TAF to AvnFPS without actually sending it out of the office?

This question is usually asked by a WFO when there is a new TAF to be issued by the office in the next few months and the forecasters want to practice monitoring and issuing forecasts for the new site well before the actual day arrives to officially issue them to the outside world.

AvnFPS doesn't actually perform the actions to disseminate your aviation forecasts to the NWS WAN or the NWWS. That's the job of handleOUP.pl: a script that AvnFPS transmission server invokes when it wants to issue products found in its pending queue. The handleOUP.pl script consults several files to determine: 1) Proper WMO identifier for the product; 2) whether the product should be sent on the NWWS; 3) and whether the product should be sent on the WAN.

Another action handleOUP.pl script performs is to store the product into the local text database.

Your Aviation focal point or ITO should use the AvnFPS configuration GUIs to create the required configuration files for the new product. Here are the steps to perform on px2 as user "fxa":

Use the AvnFPS configuration GUI "Taf Site Info" to create the necessary configuration file for your new TAF. Be sure to fill in all required text fields, especially the AFOS and WMO ID text fields. Look at other official TAF sites if you are unsure of what these identifiers look like. Save your changes.
Use the AvnFPS configuration GUI "Taf Product" to either add your new TAF to an existing group or create a separate, new group with the new TAF its sole member.
Use the AvnFPS configuration GUI "Triggers" to add the new METAR and TAF triggers to your text database. Make sure the TAF and METAR text fields are filled in for the new TAF and press "Make" to create the database triggers. [If you have problems with this step, see 3.1 Lessons Learned, second bullet]
Using your favorite text editor, open the /awips/fxa/data/afos2awips.txt text file. Here you will need to insert a new line consisting of the AFOS identifier of your new TAF in the first column, and its corresponding WMO ID in the second and third fields. Save your changes.
Using your favorite text editor, open the /data/fxa/workFiles/wanMsgHandling/NWWS_exclude_CCC.txt file (CCC is your office three-letter identifier). Here you will need to insert a new line consisting of the AFOS identifier of your new TAF. By having this entry in here, you will block the sending of your new TAF onto the NWWS.
Using your favorite text editor, open the /data/fxa/workFiles/wanMsgHandling/WAN_exclude_CCC.txt file. You may have to create it. Many offices do not seem to have this file by default. Here you will insert a new line consisting of the AFOS identifier of your new TAF. By having this entry in here, you will block the sending of your new TAF onto the WAN.

Your Aviation focal point or ITO should repeat the last three bullets on px1 machine as well to take care of the case of px2 failover to px1.

Finally, for all these changes to take effect, bounce the AvnFPS servers.   You will need to be user 'fxa' on any Linux workstation to do that:

    % /awips/adapt/avnfps/bin/remoteServers.sh restart

Restarting or bringing up a new AvnWatch GUI will show the new TAF site--if its in the DEFAULT group, otherwise, use the "Backup" button to select the group your new TAF is in. Initially the TAF button will be red and the monitoring lights greyed out due to the absence of metars and tafs to decode for that site.   Either be patient for the next metar for your new TAF to arrive, or request it from the text database using the avntrigger.sh script.   As any user run the command:

    % /awips/adapt/avnfps/bin/avntrigger.sh CCCMTRXXX where CCCMTRXXX is the AFOS identifier for the metar at the new TAF site.

At this point, you should be able to compose your first TAF for the new site.   It will have to be "Sent" in order for it to be monitored in AvnFPS. Once you've done that, AvnFPS monitoring lights will return to "normal".

When your office is ready to issue the new TAF officially, your Aviation focal point or ITO should remove the TAF's AFOS entries from the NWWS_exclude_CCC.txt and WAN_exclude_CCC.txt files on both px1 and px2 machines.

It is good practice to look at the handleOUP.log files in /data/logs/fxa/YYYYMMDD directories on px2 (or px1 in case of failover) to see the actual dispensation of your text products.

[Return to Top]    [<][>]   [<<][>>]

AvnFPS3.2 FAQs

1. Installation

2. Setup

3. AvnWatch Features

4. Troubleshooting

5. Other

Installation

Setup

AvnWatch Features

Trouble Shooting

Other Questions