Local News

Local Developers - updated 1/6/04

For local applications running on the lx systems that are written and distributed between WFOs, the maintainer/developer of the code should check for the following conditions (in preparation for the individual user accounts (OB4 requirement - deployment in Aug/Sept 2004):

1) Make sure the application does not start a persistent process. The local applications need to make sure to start and stop all processes launched.
2) Any shared files created need to be checked for file protections and permissions. Please inspect code and make sure that files have group writable permissions where needed. This includes redirecting output, script commands such as "cat" and "touch", and compiled code.

Ed Mandel (LAWG) - 301 713 - 1768 x153

AWIPS Local Applications Listserver - updated 5/1/00

This LISTSERVER was implemented to facilitate the distribution of information regarding AWIPS Local Applications. It should be easy for persons involved with local applications to broadcast new developments and important changes. All you have to do is send an email message, and that message will be routed to all interested subscribers after a quick review process.  Click here to learn how subscribe or unsubscribe.

Snuffle Update - updated 4/18/00

There have been a few incidents in March where Snuffle has been singled out for some extreme CPU usage at a few sites (e.g., BRO, LCH, FWD)  Analysis has shown that the problem is not with Snuffle but bad products being ingested by Snuffle  Mike Coyne (CRP), the developer of Snuffle, has been testing a new version which among other enhancements includes modifications to allow Snuffle to exit gracefully when bad products are ingested  Over the next few months, the LAWG will work with the developer to test Snuffle at a few sites before general release.

Local Application Use of Informix dbspace - updated 4/18/00

The current AIFM (Version 2.0) does not address the creation of local databases within Informix  However, sites have inquired about how this might be done. The LAWG asked the Software Engineering Group (SwEG) to establish guidelines and make a recommendation concerning local database creation. The SwEG recommended that local sites should not use any existing Informix database space  The SwEG cautions that, at this time, it would be risky to allow database disk space for the creation of site-local databases since there is no Informix database space allocated for this purpose. In addition, new database creation consumes /root disk space by default, and this is not at all advisable. The LAWG will establish a requirement for a site-specific dbspace for Release 5.1 and update the AIFM with this new guideline.

AWIPS Local Application Database - updated 4/18/00

On April 12, 2000, the AWIPS Local Application Database (LAD) became operational  It can accessed through the AWIPS Local Application Development web site at LAD, by clicking the "Application Database" button.

The database was developed to support the submission and registration of local applications as required by the AWIPS Local Application Policy (LAP). The database acts as a central distribution point for local application software and documentation. The database will enhance communication between the developers and users (sites), facilitate the sharing of local applications, and allow the regions and headquarters to monitor local application software development and usage.

Performance Tools and Information - updated 4/18/00

Contact your LAWG representative for site performance information like site- specific CPU utilization, triggers, etc  The AIFM Appendix 6 explains how a site can use tools to monitor application performance and resources.

Local Application Development Training - updated 4/18/00

The NWSTC Engineering Division is conducting an AWIPS Local Applications development training course  Next course is in May 2000.  The objectives are to provide developers the information and tools necessary to design, build, and test local applications on AWIPS. Focus will be on AWIPS-specific data access, programming tools (Perl and Tcl/TK) and information to enable development, and porting of local applications to AWIPS.  For more information see the NWSTC Engineering Division web page at
www.nwstc.noaa.gov/d.train/AWIPS.HTML#M2001

Application Integration Framework Manual (AIFM) - updated 4/11/00

The LAWG has completed updating the AIFM standards and guidelines. Updates include:  (1) reviewing and tightening-up of the AIFM guidelines and standards; and (2) updating the external documentation requirements (Section 3.8 and Appendix 4)  A new version of the AIFM (Release 4.3, Version 2.0) is available at the AWIPS Local Applications web page.

CAFÉ - updated 3/9/00

CAFE uses the SLC AWIPS TCL scripts written by Dave Toronto to form the basis for formatters that generate voice ready messages that are ftp'd to CRS. The idea is to have a nationally supported AWIPS script formatter that will supplement the AWIPS baseline formatters until the latter can satisfy all requirements.  The CAFE scripts are being modified and corrected based on alpha testing at Norman (installed 2/14).  Additional products are being added to support marine and other requirements.

Local Application Disk Space for Release 4.3 - updated 2/29/00

An additional 1Gig partition on vg02 for local application data will be available in the Release 4.3 time frame.  The System Engineering Team (SET) is currently going through an exercise to reevaluate local application disk space for Build 5.

COTS/Freeware - updated 2/29/00

The SwEG has approved the following COTS/freeware packages for use on AWIPS.  Use of this software should be done in accordance with the Local Application Policy and AIFM.

ArcView - The local use of Arcview is approved with the following caveats; (1) all RFCs install in a similar fashion (i.e., same directories,etc), and (2) as the sites get experience with Arcview on AWIPS - especially as regards performance impacts - that information be passed back to the SET via the LAWG.

Java - The local use of Java is approved at selected sites only and must be coordinated through the LAWG  Pending results from these sites, general allowances for all sites will be considered.

Perl/Tk - The local use of Perl/Tk is authorized at all sites and should be done in accordance with the guidelines in the AIFM.  Perl/Tk will not be included into the national baseline at this time.

SAMBA - The local use on the LDAD server is authorized at all sites and should be done in accordance with the guidelines in the AIFM.  SAMBA will not be included into the national baseline at this time.

LDM - The local use on the LDAD server is authorized at all sites and should be done in accordance with the guidelines in the AIFM.  LDM will not be included into the national baseline at this time.

Python - The local use of Python is authorized at all sites and should be done in accordance with the guidelines in the AIFM.  The SwEG suggests that the sites use the same version to be provided in the baseline for Release 5.0 (Version 1.5.2).

Shapefiles - updated 1/19/00

Shapefiles exist at the site, usually in nationalData.  Copies of them exist in the catalog.  If sites are writing c or some other high level code for local applications, they must read the shapefiles directly. See http://www.esri.com/library/whitepapers/av_lit.html and you'll find ESRI Shapefile Technical Description White Paper Date: July 1998 Subject:  This paper defines the shapefile data format.  It also provides all the technical information necessary for writing a computer program to create shapefiles without the use of ArcView GIS or other ESRI software for organizations that want to write their own data translators. (126 KB/34 pages).  With this document, you'll be able to write code to create a module to read shapefiles to be used in your local programs.

FPCMAP Decoder - updated 1/7/00

FPCMAP ia an application developed by WFO Tulsa that creates a regional map of FAN and FWC guidance numbers.

A minor bug was recently discover in the FPCMAP application.  The bug is not Y2K related and is isolated to a routine in the decoder program fwcdec.exe.  The bug could result in the improper display of FAN guidance on the main fpcmap display with FAN temperatures or POPs with 3 digits (e.g., 100 POP or -20 Temp).  The NGM MOS guidance values in the FWC bulletins were decoded correctly and were not affected by this bug.

To get an updated decoder, send a note to geogory.patrick@noaa.gov and a copy will be sent.  Or if you prefer, do an anonymous ftp to the following server and change to the appropriate directory: 192.133.17.151 cd pub/wfotulsa/SHARE

XNOW Version 2.1 - updated 12/20/99

Xnow version 2.1 has been released.  You can download the program and view the installation instructions from the official Xnow Web site at http://www.srh.noaa.gov/ama/xnow/default.htm.  Xnow version 2.1 contains mostly bug fixes.  The most significant fix is for a Y2K problem that was discovered recently.  This Y2K error causes the UGC expiration time clock GUI to fail.  For this reason, I recommend that you upgrade to version 2.1 prior to Dec 31st.  If this is not possible, you can easily patch the program by editing the tcl code of your existing version.  Xnow version 2.1 also corrects a handleOUP.pl utilization error and the afos2awips.txt file to properly build the command-line for handleOUP.pl.

Local Applications Home Page