Date: 05/12/2006
|
Release |
Title: |
Reference Number: |
|
OB7.2 |
FWF: Enhancements (Add options for regional formats (ReqReq)) |
DCS
3353, tk4482 |
|
Contacts |
Name |
Email/Phone |
|
Task Lead |
Mark Mathewson |
Mark.A.Mathewson@noaa.gov |
|
Main Developer |
Tracy Hansen |
Tracy.L.Hansen@noaa.gov |
|
Documentation Focal Point |
Mark Mathewson |
Mark.A.Mathewson@noaa.gov |
|
Testing Focal Point |
Mark Mathewson |
Mark.A.Mathewson@noaa.gov |
|
Narrative: |
|
This is a GFE Text Formatter Enhancement for the FWF product. Each region wants a slightly different format/contents for the FWF product, which is allowed by the national product directive. This change allows for more regional formats to be produced by the baseline FWF formatter. |
|
Milestone |
Date |
|
Requirements Review |
04/17/2006 - conference call.
Participants: Mark Mathewson (GSD), Tracy Hansen (GSD), Doug Young
(OCCWS), Joe Palko (ER), Matt Belk (ER), Jeff Manion (CR), Eric
Howieson (SR), Kirby Cook (WR), Michael Szkil (Training), Chris
Marshall (Raytheon/Keane), Andrew Lare (Raytheon/Keane), Ed Mandel
(SEC). Accepted without changes. |
|
Design Review |
04/17/2006 - conference call. Participants: Mark Mathewson (GSD), Tracy Hansen (GSD), Doug Young (OCCWS), Joe Palko (ER), Matt Belk (ER), Jeff Manion (CR), Eric Howieson (SR), Kirby Cook (WR), Michael Szkil (Training), Chris Marshall (Raytheon/Keane), Andrew Lare (Raytheon/Keane), Ed Mandel (SEC). Accepted without changes. |
|
Interface Review |
NA |
|
Test Plan Review |
TBD |
|
Independent Testing |
TBD |
|
Integration (GFS Handoff) Readiness Review |
TBD |
|
Documentation Turnover |
TBD |
|
Software Check-In (GFS Handoff) |
TBD |
|
References/Attachments |
Location & Document Name |
|
Requirements Documentation |
Integrate
enhancements from ARX into the baseline FWF allowing more regional
preferences to be easily configured in the baseline product. The
default baseline behavior will not change. |
|
Design Documentation |
All changes are confined to the GFESuite Text Formatter infrastructure. Here is a list of changes to be added to the baseline from Matt Davis/Dan Baumgardt at ARX. They have a version of overrides which can be used to implement these options. 1. Periods:Baseline: Includes .OUTLOOK... NC: Does not include .OUTLOOK... 3. Elements in short term periods A. Sky/Weather Baseline: Includes sky cover percentages. Does not include PoP phrase. NC: Does not include sky cover percentages. Does include PoP phrase for entire period. 3 hour sampling. (ie. CHANCE OF RAIN 30 PERCENT) B LAL Baseline: Includes NC: Does not include C. Max or Min Temperature/Max or Min RH: Baseline: Gives "AROUND XX" NC: Gives 5 degree/percent range centered on zone average. D. 24 Hour Trend: Baseline: Includes 24 Hour trends for RH and MaxT/MinT NC: Does not include trends E. 20 foot winds: Baseline: 6 Hour samples NC: 3 Hour samples F. Haines Index Baseline: Includes "POTENTIAL FOR LARGE PLUME DOMINATED FIRE GROWTH" wording NC: Only includes value and category "HAINES INDEX: 5 OR HIGH" G. Hours of Sun: Baseline: Does not include NC: Includes based on potential hours for the day and sky cover average. H. Precipitation: Baseline: Does not include NC: NONE or AREAL COVERAGE QPF phrase. "SCATTERED 0.25 TO 0.50 INCH AMOUNTS" I. Humidity Recovery: Baseline: Includes NC: Does not Include J. Mixing Height: Baseline: Range through period. Includes at night. NC: 12 PM to 6 PM LT Average, one value. Includes phrase "(AVE 12 PM TO 6 PM). Not included at night. K.Transport Winds Baseline: Includes NC: Includes, with the (AVE 12 PM TO 6 PM) phrase. Not included at night. L. Smoke Dispersal: Baseline: Includes category range, then numeric value with units "POOR TO EXCELLENT (3000 TO 180100 KT-FT)" NC: Includes average value and category and (AVE 12 PM TO 6 PM) "AROUND 124000 OR EXCELLENT (AVE 12 PM TO 6 PM)" M. Chance of Wetting Rain: Baseline: Includes. NC: Does not Include 4. Elements in the Extended Periods Baseline: Winds (Early Extended Periods), Sky/Wx, MaxT/MinT. NC: Winds (All Extended Periods), Sky/Wx, MaxT/MinT, PoP Phrase. 5. General NC Formatter has a switch to turn off Mixing Height, Transport Winds, and Smoke Dispersal when not needed in Summer. |
|
User Interface Documentation |
NA |
|
Code Review Summary |
|
|
Test Plan and Procedures |
See
OB7.2 GFE Test Matrix |
|
Summary of Functional Testing |
|
|
User Manual and SMM Documentation |
No changes needed to User Manual and SMM
document. GFE User and System documentaion is provided with the
software release and is available at:
http://www-md.fsl.noaa.gov/eft/AWIPS.html |
|
Integration (GFS) Handoff Checklist |
This document. |
|
Id |
Question |
Response |
|
I. |
Design/Architectural Assessment |
|
|
I.1 |
List names of new persistent processes if any. If none, state "NA". |
NA |
|
I.2 |
List names of existing persistent processes that will require mods if any. If none, state "NA". |
NA |
|
I.3 |
Does design include new fork/exec calls, system calls, or threads? If so, list type; also identify process(es) performing such activity. If no such calls will be made state "NA". |
NA |
|
I.4 |
If item will involve new processes, describe how processes will communicate (e.g., sockets, pipes, signals). If no new multi-processing involved state "NA". |
NA |
|
I.5 |
List all languages being used. |
Python, C++ |
|
I.6 |
Are new versions COTS/freeware being used (Yes/No/unsure)? |
N |
|
I.7 |
List any AWIPS system APIs/CLIs anticipated being used (e.g. textdb, distributeProduct, handleOUP, transferNWR, ...) If none, state "NA". |
NA |
|
I.8 |
Describe any new AWIPS system APIs/CLIs desired but not currently provided. If none desired, state "NA". |
NA |
|
I.9 |
Describe any modifications to existing AWIPS system APIs/CLIs desired. If none, state "NA". |
NA |
|
I.10 |
Mark (Y/N) any planned use of the following AWIPS services: NotificationServer, TextNotificationServer, PostGres triggers, Postgres (general) , MHSserver , DataController , CommsRouter, any core system Decoders (identify which). |
N |
|
II. |
Database |
|
|
II.1 |
List existing databases to be read from. If none, state "NA". |
NA |
|
II.2 |
List existing databases to be written to. If none, state "NA". |
NA |
|
II.3 |
List modifications to the format of any existing databases. If none, state "NA". If yes, include information about conversion scripts, disk space requirements for backup, conversion and reload, estimated time for conversion and ingest downtime requirements. |
NA |
|
II.4 |
List any new databases and their proposed type (Informix, UNIX file). If none, state "NA". |
NA |
|
III. |
Operability |
|
|
III.1 |
Will a new user interface be implemented (Y/N)? |
N |
|
III.2 |
Will an existing user interface be modified (Y/N)? |
N |
|
IV. |
Application Integration and Installation |
|
|
IV.1 |
Have new or changed metadata files been used (Y/N/unknown)? If yes, provide information about site-configuration, merging with existing customizations, and need for re-localization. |
N |
|
IV.2 |
Is localization required (Y/N/unknown)? If Y, list localization options. |
N |
|
IV.3 |
Have runtime setup files (.rhosts, .environs, etc.) been chnaged (Y/N/unknown)? |
N |
|
IV.4 |
Are there any new exes/scripts/data/config files (Y/N/unknown)? If Y, list the file location (directory, host) and their permissions. Will the old files need to be converted and is the change backward compatible? |
N |
|
IV.5 |
Is any cron usage anticipated (Y/N/unknown)? If Y, list times of day if known. |
N |
|
IV.6 |
Have the appropriate mkdirs and purge scripts been modified? |
NA |
|
V. |
System Integration |
|
|
V.1 |
Will the functionality get installed at all site types (WFO/RFC/OCONUS)? If N, are all site type-specific files available (acq_parms, menus, etc.)? |
Y |
|
V.2 |
Are there changes required to dtwmrc or other environs files? (Y,N,unknown) If Y, list the changes. |
N |
|
V.3 |
Does a previous version of the function need to be installed prior to this version? |
N |
|
V.4 |
Are there any old files/data that need to be removed from the site? (Y, N/Unknown) If Y, is removing these files optional or will the system be unstable? |
N |
|
V.5 |
Are there any dependencies or sequencing that needs to followed during installation and integration? |
N |
|
V.6 |
Is SBN use expected (Y/N/unknown)? If Yes, is the expected usage known - e.g., frequency and times of use, amount of data, etc. (Y/N/unknown)? Provide details. |
N |
|
VI. |
Performance |
|
|
VI.1 |
Will remote system calls (e.g., rcp, rsh, etc.) be used (Y/N/unknown)? If Yes, list |
N |
|
VI.2 |
Is there any new NFS access? |
N |
|
VI.3 |
Is there any new data acquisition? Is there any impact on disk space? |
N |
|
VI.4 |
Is there any new WAN access? If WAN use is expected, is level of usage known - e.g., frequency and times of use, amount of data, etc. (Y/N/unknown)? If Y, provide details. |
N |
|
VII. |
External Interfaces |
|
|
VII.1 |
List name(s) of all external interfaces this item will directly contend with; do not list interfaces for which an AWIPS-provided API/CLI exists, such as distributeProduct, transferNWR). If none, state "NA" |
NA |
|
VII.2 |
For every external interface listed in III.1 does a formal and sufficient Interface Control Document (ICD) exist (Y.N)? |
NA |
|
VIII. |
Documentation |
|
|
VIII.1 |
Will SMM entry/mod be required (Y/N/unknown)? If Y, please state section, type of change (e.g. new, modified) and location of soft copy (if available). |
N |
|
VIII.2 |
Will Users Manual entry/mod be required (Y/N/unknown)? If Yes, please state section, type of change (e.g. new, modified) and location soft copy (if available). |
N |