These are the Build 4.3 "routine update" tasks for FSL. As you'll see, this is mostly just a text listing at the moment.
1. Alert Area Request Changes
Description :
a. Eliminate duplicates in area, categories, and thresholds
b. Enable the application to switch from one radar to another
radar (for sites that have more than one dedicated
connection) and maintain separate area definitions,
categories, and thresholds for each area.
c. Add the capability to have an area defined without any
categories/threshold, in which case no information
is forwarded to the RPG i.e. no alerts are generated.
Scope of Changes:
Est. Development effort: 4 weeks
Code into PCMS:
DRs: 2664 - Alert Area deficiencies
2. Radar system/status message
Description :
a. Add the capability to deduce from
the general status messages those instances where the communications
line to the RPG has gone down and stayed down for more than a
minute.
b. The user shall be notified of this condition by the
radar subsystem popping a red banner message on the graphic
workstation screens.
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs: 1299 - Radar status bar carries too many messages
3. Clutter Filter Control maps
Description:
Correct the display of clutter filter control maps. Currently
the CFC displays, but we are not sure it is the same information
as displayed on the PUP.
a. Verify PUP display of CFC data
b. Modify display of CFC in AWIPS if necessary.
Currently the CFC displays, but we are not sure it is the same
information
as displayed on the PUP.
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs: none
4. Radar status messages
Description:
a. When the dedicated line is connected for a radar, output the
status message decoded from the GSM in the radar status box.
b. Any subsequent GSMs received by the radar will ONLY be put in
the status box if there is a change from the previous message.
However, the "mode" message will always be printed.
c. For dialout, the GSM will only be printed if the rda is out of
operation or the rpg is inoperable. Only severe messages from the
dialout radar will prompt the GSM to be decoded and information
written to the RADAR_Announcer file.
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRS: none
5. RMR changes
Description:
a. When sending out an RMR request, the radar status message needs to
print
"Sending Request ....
b. When the process, wfoApi, actually sends out the
request, it will write "Request sent successfully" in the radar
status box.
Scope of Changes:
Est. Development effort: 5 days
Code into PCMS:
DRs:
4285 - RMR not receiving SRM product
6. One Time Request
Description:
a. Modify request for cross sections
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
4014 - Add az/ran to cross section OTR GUI
4015 - Cross section distance must be at least 1 km
4016 - Add 8 level cross section products to OTR
3774 - OTR dial radar only lists 46 radars
7. Radar Storage
Description:
a. Modify RadarStorage so that it checks for VCP 11 and VCP 21
(precip) instead of Clear Air (VCP 32). This change is necessary
since there are two clear-air VCPs, 31 and 32.
b. DR ???? - We need to add "^SDUS5.*" to the RadarStorage patterns
file, so RadarStorge gets notified when radar data arrives from the
SBN.
c. DR ???? - The RadarStorage process doesn't seem to turn off
dissemination of radar products to the WAN when the radar changes
from storm to clear-air mode.
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
DRs ????
8. Radar Ingest
Description:
a.The ingest process, wfoapi, needs more descriptive status messages
displayed on the radar status window (bar).
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
3956 - Renice wfoApi to 15 to ensure timely receipt of radar data
4049 - Analog line disconnect leaves line in pending state
3756 - Maintenance RPS list not created during localization
4173 - Process should not write logs in awips/fxa/bin
9.Radar WAN
Description:
a. The RCM header may not contain the right WMO id for all of the
sites. It came out a few weeks ago that some sites should be
using a legacy id of SDUS99 KWBC, which isn't what we implemented.
b. Radar data is being sent to the WAN with a "normal" priority
(priority 1); they probably should be sent with a low priority
(priority 0).
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
10. Radar Display
Description:
a. Make changes to the raster radar depictable so that it works the
same as radial depictables by allowing style information to come
from a table for color bar information like other images and then
only if that fails will they try to get it from the header or
based on internal calculations.
b. Correct the display of clutter filter control maps. Currently the
CFC displays, but we are not sure it is the same information as
displayed on the PUP.
c. Create a new mapping table for products which are
exactly 360 radials
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
3576 - DHR product mislabeled
DR ???? - VR shear to work with 8 level products
DR 3559 - Optimize number of radials assumed in radar mapping table
3773 - Dial radar menus not in alphabetical order
1. Decoders
Description:
a. Add a raob netcdf file. There is currently no netcdf file
for the compressed BUFR raob data. For local development this
b. Remove the ldad plot files.(change the depictable
software to use the existing netcdf for the hydro data plot).
This would eliminate a process on the ds and be a performance
enhancement.
c. Update SAW decoder module to understand either the old or
new SAW format anticipating watch decentralization.
d. LDAD storage of netcdf consumes too much CPU time.
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
3888 Ldad storage of Netcdf and Plot files consumes too much CPU time
4000 Metar Decoder crashes with metarsignalclient.c error
4149 Metar decoder hang - as1 CPU utilization goes to 80%
2063 binLightningDecoder performance problems
2922 Maritime Decoder does not decode maximum gusts over last hour
2707 The grids from the UK met office do not decode properly because
they send "thin" grids
2. Data Retention
Description:
a. Add a timetimed-based purger. Add another capability for purgers
that deletes not on number of versions but on a timed basis
(similar to the LDM "scour" function).
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
4289 Scour deletes some hydro products before they can be decoded
3. Text Database
Description:
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
3481 Military METARs are not tagged with METAR or SPECI when stored
3702 Textdb Reader crashing at OUN
4. Router/Controller
Description:
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
3373 Y2K DataController logs stop, but do not restart
5. Data Acquisition
Description:
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
2496 acqservers do not clean up old/dead processes and logs
1. Archive Manager User Interface
Description
a. Change to always displaying the tree views collapsed initially.
b. Cont store enabled button should be disabled whenever the product
selections are being changed, but only if cont store is off.
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs
3688 When dispaying a case the time range for the case is not
displayed. 3689 Cont store tree view not initializing correctly.
3716 "Needed" disk space for restore displays as zero MB if less than
one MB is needed.
2. Storage
Description:
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
3684 Old media sessions are not removed from the database
3. Restore
Description:
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
3522 - Restore does not work for time ranges greater than
72 hrs
3595 - The time range editing dialog for restore is not
initializing correctly
3686 The "Time Subrange" setting for restore does not work
3996 - Selections for restore causes continuous store to be
disabled
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
4. Archive Manager
Description:
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs
3994 - Running two or more archive managers does not work
correctly
5. Display of archived radar data
Description:
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
4087 - Only 1 archived radar product can be shown at a time
when D2D is in Archive mode
1. Extensions
Description:
a. Add the capability to print extension output.
b. Modify function of distance/speed of motion such that the dot or
line appear in the center of a zoomed display similar to the
behavior of warngen. In current implementation they default
to last position.
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
2. Map Backgrounds
Description:
a. dim map background selectors based on scale
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
3. Depictables
Description:
a. Add hurricane track plotting program using TCM text messages
b. Profiler perspective display needs to be corrected for initial
display
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
4. Menus
Description:
a. Enable magnification from popup menu for extensions
b. finish removing xmain
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
5. Three pane layout
Description:
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
1680 When viewing radar composites with D2D's Three Pane
Layout The X server tops out CPU usage.
6. Announcer
Description:
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
1732 D2D system and radar announcements occasionally become
unaccessable.
7. Miscellaneous
Description:
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
2542 When using Forced load mode an inventory window does not appear
2674 alarm/alert sound
1. Wording and Formatting
Description:
a. An option to leave out the time zone in time formating.
b. For the default version of SVR and TOR, improve formatting for
single versus line of storms.
c. Make speed below which storm is considered stationary adaptable,
as well as the wording used to describe a stationary storm.
d. Make wording for describing a line of storms adaptable instead of
hardwired in the code
e. Allow the units of the distances described to be adaptable
f. Warngen is designed to default to another description if no
cities at all make it into the pathcast, but this is not working,
I would like to debug this.
Scope of Changes:
Est. Development effort: 14 days
Code into PCMS:
DRs:
2. Display
Description:
a. Make two points the default for the line of storms tracker.
b. Option to just describe the endpoints of a line of storms regardless
of how many vertices
Scope of Changes:
Est. Development effort: 3 days
Code into PCMS:
DRs:
4136 Large Combined Home CWA and Partial Backup Coverage
Causes Anomalies
3. Obsolete capabilities
Description:
a. Just get rid of the stuff that allows one to revert to the old
SRWARN format...I have been assured that noone will ever need it
again.
Scope of Changes:
Est. Development effort: 3 days
Code into PCMS:
DRs:
1. Keyboard
Description:
a. Add text keyboard accelerators to load previous/next version
of currently displayed text product. It should operated the same
as the previous/next menu selections, including null operation
if multiple products have been loaded.
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
2. User Interface
Description:
a. 4 character station ID support in text workstation help
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
3077 - Dialog box on text workstation: Expiration time should
be noted as Z time.
3. Alarms
Description:
a. Make alarm/alert behavior more consistent
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs:
1903 - Text Alarm/Alert sometimes fails on receipt of initial
product
1. Installation
Description:
a. Put some logic into the localization scripts so that they
recognize when certain tasks do not need to be redone because
the files involved are already up to date.
b. Tightly control the updating of .sup files in the localization so
that only when their contents change will their file create time
change. Purpose of this is to encode the sup file create time into
the depictorName in data files. This will fix a bug that sometimes
occurs when the localizations on the data server and workstations
are out of sync.
Scope of Changes:
Est. Development effort: 5 days
Code into PCMS:
DRs:
1. Display Description: Scope of Changes: Est. Development effort: Code into PCMS: DRs 2058 - LARC data is not displaying 2. Ingest / Dissemination Description: Scope of Changes: Est. Development effort: Code into PCMS: DRs: 3403 - Sometimes pollForData.pl hangs and takes up all available resources 3641 - The ldadScheduler does not indicate whether request are successful (or not). 4055 - LDAD ROSA will not accept data on Feb 29, 2000 (leap year) 4129 - LDAD Auto faxmodem will not fax all products. 4209 - Could not get XYZ-modem dissemination to work from the LDADScheduler 2534 - LDAD External processes occasionally exit 3. Monitor Description: Scope of Changes: Est. Development effort: Code into PCMS: DRs: 3614 -LDAD admin can not correctly modify MSAS reject and accept files 4. Installation Description: Scope of Changes: Est. Development effort: Code into PCMS: DRs: 4251 - Security hole in root's path 3231 - LDAD binaries are being put into the fxa/bin and fxa/data staging area. 5. Logging Description: Scope of Changes: Est. Development effort: Code into PCMS: DRs: 4278 - There are multiple logs per LDAD process. 4134 - rosamodem log reports errors all the time
1. Site Ids Description: Scope of Changes: Est. Development effort: Code into PCMS: DRs 996 - MHS cannot handle 4 letter site id 2. Product transmission Description: Scope of Changes: Est. Development effort: Code into PCMS: DRs 3651 - 1st attempt sending message w/attachment fails 3820 - Requests not "queued" when MhsRequestServer is down
1. Logging
Description:
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs
3913 LAPS Stops Running and Fills Up Logs Directory
2. Failover
Description:
Scope of Changes:
Est. Development effort:
Code into PCMS:
DRs
3978 First attempt at using message handling after swapping to
DS2 fails
3945 Green times and auto-updating break after swapping as1 to
as2
4095 No new green time and autoupdate of looped data
1. Process monitor Description: Scope of Changes: Est. Development effort: Code into PCMS: DRs: Process monitor does not monitor notification server