AWIPS Build 4.0 Release Notes

Graphics Workstation Enhancements

New user interface

• The menu and tool bars extend all the way across the display. While this slightly reduces the size of the monitor panes, it accommodates pane resizing. The tool bar can be removed to make the display windows larger (toggle the Tool Bar button in the View menu); all tool bar functions are replicated in the menus.
• Panes can be resized by dragging on their borders. There is a limit as to how far you can drag to the right (about 40% of the width), so the main pane is always the largest. If you drag a horizontal border to the bottom of the display, you can nearly eliminate one or two of the monitor panes, effectively yielding a two- or three-paned layout. Icon buttons for the default layout and a preset 3-pane layout are available on the menu.
• Icons are used for most tool bar commands. If you put the pointer over an icon, a help string will appear in a couple of seconds to remind you of the button's function.
• The history list is now directly on the File menu, no longer hidden in the Procedures cascade menu.
• A Print icon is used for default printing. Printing options are still on the File>Print... menu.
• Section headings in menus are in a contrasting color, to ease menu navigation.
• Changing scales is much faster than in Build 3. Also, you get menu control almost immediately after a Clear.
• Time-resolution loading is now available from the Options menu, not as one of the load modes. If data inventories support it, you can use time-resolution load along with any of the load modes.
• Keyboard accelerators have been added for several functions. The list includes:

  Menu Functions			Display Functions
  Key	Function		Key	Function
  Ctrl+n	new procedure		left arrow	step back
  Ctrl+o	open procedure		right arrow	step forward
  Ctrl+d	delete procedure		Ctrl+left	first frame
  Ctrl+h	history		Ctrl+right	last frame
  Ctrl+p	print w/options		up arrow	loop faster (turn on if not)
  alt-F4	exit/ close dialog		down arrow	loop slower (turn on)
  Ctrl+c	clear		Keypad 0	toggle image
  Ctrl+l	loop properties		Keypad 1-9	toggle overlays 1-9
  Ctrl+i	image properties		shift-Keypad 0-9	toggle overlays 10-19
  F12	where's that cursor? (the "Martha" button)		Keypad .	image 1/2 toggle
  Insert	toggle image combo		Keypad +/-	image fade
  			Keypad Enter	3-way legends toggle: 1. standard 2. time only 3. maps

  Note: In order for these accelerators to be used, the display window (or any properties dialog) must have focus. That is, its border must be colored. Tear-away menus are not included; you can use the arrow keys in those to navigate through the menus - the right arrow opens cascades. If your pointer is over an application menu (e.g., the Volume Browser), you also can't use the keyboard accelerators. (This same point applies to the text window that you can use on the graphics screen; you can't type commands there unless it has the colored border indicating focus.)

  Note 2: Accelerators for image combination and loop toggle are not indicated on the menus.

Other new features

• You can now delete user-created color tables. To do so, display the table you wish to remove, then select Delete... from the Image Colors Editor application's dialog.
• The startup process has been changed. Now, the large pane comes up first, before the monitor panes are started. Once the map is visible on the large pane, you can load products, without waiting for the monitor panes to display. This lets you view data within about a minute of starting.
• If an IGC (display process) crashes, it will restart automatically. This eliminates most occurrences of a black, unusable, monitor pane, and should greatly reduce the number of restarts required. If a restart occurs, you'll get a red-box message so indicating. A new item on the Options menu allows you to restart any display panes that have died (though in many cases it erroneously indicates that all panes are running normally, when in fact they are not).
• A new fixed buoy plot is added to the Surface menu.
• A wind chill/heat index plot is also added to the Surface menu. Wind chill is displayed for stations whose temperature is below 60F, and heat index for the others.
• There are six new pop-up menu features, in three classes:
  1. You can change the panel layout between single and four panel. When you enter 4-panel mode, the products currently displayed are put in the upper-left panel. When exiting 4-panel mode, the products in the panel over which you popped up the menu will be loaded into the single panel.
  2. Multiple unloads (applies to small and large panes):
     • Unload All Products - all products and user-loaded maps
     • Unload Graphics - all graphics products and user-loaded maps
     • Unload Extra Maps - all user-loaded maps
  3. In small panes, the pop-up now includes a "Step Frame" cascade menu containing step forward, step backward, first frame, and last frame icons.
  4. A lat/lon cursor readout is now available (any pane).
• You can select two fields in the Volume Browser and display their difference.
• The Volume Browser will now display a grid time series at a named point.
• A storm summary product suite (tornadoes, large hail, severe gusts, each in its own overlay) is added to the Surface menu. Events are extracted from the STADTS and STAHRY products, and plotted to time-match the current display. (If displayed stand-alone, the entire contents of each STADTS/STAHRY version will plot in successive frames, thus producing a generally hourly plot.) Sampling these products yields descriptive text for the events.
• New Z/SRM menus are added to the radar menu.
• The 1 km composite reflectivity product on the main radar menu is now called simply "composite reflectivity," and is a mosaic of 1 km and 4 km data (depending on range). The individual 1 km and 4 km products are still available on the "Derived" menu. A VIL/composite reflectivity product is also added to the main radar menu, where these are mosaiced in the same way as the 1 km/4 km composite reflectivity products.
• A new vrShear extension is available on the Tools menu. It lets you read gate-to-gate (or other point-to-point) radial velocity shear.
• New on the radar menu are buttons to load all tilts in successive frames, to provide a loop passing from low to high tilts. In conjunction with this, the 3.4/3.5 deg tilt products have been moved into the "Hi Z/V/tilts" cascade menu (to reduce the length of the main radar menu).
• You can now interrogate cursor position information from skew-T backgrounds (both hodograph and temperature/pressure areas).
• Included in this build is LAPS, FSL's Local Analysis and Prediction System (though the prediction part awaits a future build, requiring more CPU horsepower than is currently available at WFOs). The LAPS analysis is on a 10 km grid, covering a somewhat-larger-than WFO area. These data are available in the volume browser and on the Surface menu.

Improvements

• Combined deep (multi-color) graphics no longer fade. You can still combine them (display two), but only one or the other will show.
• The storm-relative motion (SRM) product now includes the storm motion vector information plotted in the upper left corner.
• The choices on the one-time-request menus have been tweaked as necessary to conform to NEXRAD specs. Also, the OTR menu indicates in the window title whether the selected radar is accessed via dedicated or dial-in connection. The RPGs are now alphabetized in the list used here and in the RPS list application.
• The time interface in the one-time-request application has been simplified and improved.
• The product maker now can work with satellite images. It also is knowledgeable of the current display scale, and provides appropriate choices of model data.
• Tools and map backgrounds no longer carry inventory times on the menu.
• The CWA map now includes forecast office identifiers. A map of RFC areas is now available.
• When displaying map legends, the on/off state is more clearly reflected in the legend color. (Previously, "on" was dimmer than "off," which is counter-intuitive.)
• Grid items:
  • Precipitable water for Eta, mesoEta, and NGM are now available in the Volume Browser.
  • New mesoEta boundary layer products are added at 30, 90, 120 AGL. (Note that the first of these also appears on the Volume Browser menu as "BL" - either will work.(?))
  • Several additional fields are now available from the MRF. These include data at 1000, 850, 700, 300, and 250 hPa, convective precip, and wave-5 height. Also, the Northern Hemisphere and North American grid sets for MRF are now equivalent. 12-hour resolution now extends all the way to 240 hours.
  • Numerous additional AVN model fields are now available on the double-resolution grid. This will improve their displayed appearance. On the North American scale only, forecast projections for AVN now include 3, 9, 15, and 21 hours. Also on the NA scale, vertical velocity at 900, 950, and 1000 hPa are added to the menu (though data are not yet sent by NCEP for 900 and 950).
• A new IR/water vapor combination product is now available, in which IR window data replace water vapor pixels where the cloud-top temperature is below -35C. A color table for this is added to the menu.
• A new color table for the fog product (11 - 3.9 micron) is also added to the color tables menu.
• WarnGen items:
  • WarnGen now includes buttons at the top to select an alternate county warning area, for site backup purposes.
  • When a watch is in effect, a banner to that effect is now available for warnings within the watch area.
  • WarnGen now allows you to select a line of storms, rather than just a single location. While you can have as many segments in the line as you wish, each will be mentioned in the text describing the extent of the line.
    Note that there is a bug in the initial set-up of the line feature. When the default line displays, with the "Drag me to storm" prompt, you must move the whole line (drag when the pointer is in the + shape) in order to get a track. If you drag any (or all) of the vertices, you'll get a box, but no track. (You can drag the whole line at any time to get your track.)
  • In WarnGen, you can toggle the (new default) display of county/zone hatching, and generate a new first-guess box (which is based on the storm track you've defined, and is the common trapezoid shape) at any time. You can also click with button 3 on a county (or zone, depending on map background selection) to add it to or remove it from the warning area. After toggling counties, click "Redo Box" to encompass the new area.
• The Interactive Skew-T application has been re-worked. You now start the program from the pop-up menu over the display (including from small panes, but not from 4-panel displays). An interactive version of the sounding overlays your display (click button 2 over the legend to activate it), and then you can select and drag points to modify the sounding.
• Boundaries for Canadian provinces and Mexican states are now included in the States map.
• When a red box message comes up, it is (optionally) accompanied by a sound. A selection of sounds is available from the Options menu.
• Due to proximity to other stations, some stations will not display, even at the closest zoom and highest density. A new "Max" density setting is now available, to show everything.
• A new "zero" graphics magnification is also included. This will turn off all labels on contours (and will make station plots disappear except for a dot at the station).
• When you are working with an interactive-drawing polygon, and want to create a new vertex, the vertex will appear where you click, rather than always at the midpoint of the segment.

Bug fixes

• Graphics controls are now properly set with bundle loads.
• All weather symbols (SQ, at least, used to be wrong) now are correctly positioned on METAR plots.
• When you swap a blank frame into a small pane, it now properly shows no time label.
• Four-panel loads now work properly from history/procedures.
• Previously, if you hid the latest frame in a loop, then swapped, the pane would be blank until loop or step. Now fixed.
• Mapping of storm track and mesocyclone radar graphics was incorrect. It's now fixed.
• METAR precip plots are now correct. Previously, they often plotted amounts too high, due to an error in interpreting the precip code in the obs.
• Radar cross sections are back on the menu, as they now will display properly. The CFC product is also re-enabled.
• SRM cursor read-out for range folded areas now displays "RF" rather than ">50 kts".
• Previously, if you created a lot of color tables, the menu would eventually grow large enough that your new tables were off the bottom of the display, and thus inaccessible. Now, when the list of tables grows too large to fit the menu (more than 41 total tables), a cascade (pull-right) will be created to accommodate as many tables as needed.

Text workstation

New features

• It is now possible to send administrative messages (ADR) on the AWIPS Wide Area Network (WAN). A new Attach button is enabled on the Text Editor control bar when editing ADR products only, to allow attaching files to these messages.

Improvements

• Inventory times in the browser now auto-update.
• Scripts can now be renamed, via an option under the File menu of the script editor. Also, a new script no longer carries a default name. When you save a new script, you're prompted for a name under which to save it.
• The "Recover Edit Session..." dialog is extended to allow recovery of in-progress files from any workstation. Thus, if the workstation crashes and can't be restarted, you can use another to complete your editing.
• A dialog is added confirming that you really want to cancel your edit session. (This reduces the possibility of accidently trashing a product in progress.)
• The dialog to confirm your request to store a text product has been removed, as has the "do you really want to print?" dialog.
• An office suite of alarm/alert products may be set by your site administrator. You can add others, but cannot modify those from the workstation.

Bug fixes

• The default browser origin is based on the local site ID (rather than always being "West"). Similarly, the WSR CCC now appears in the default origin menu, with an appropriate list of WSRnnnxxx products when you select the Radar/Upper Air class.
• The behavior of the browser inventory process has changed. Previously, if you selected, say, MTR, then another NNN, you had to wait perhaps quite some time for the MTR inventory to display before the browser would show the new NNN's XXXs. Now, the latter will come up right away (though its inventory will still wait until the first inventory completes). The result is a much more responsive browser.
• When you are viewing the earliest version of a product and select Previous, the screen no longer clears.
• The xx.NNN command now properly includes national bit products. Also, such queries are more responsive, because they display products as they are retrieved from the database, rather than collecting them all first.
• AIRMETs are now properly split out to be stored as WAxS, WAxT, and WAxZ, instead of all being stored under WAxO [x=1..6].
• The text browser now shows essentially all products for all sites. In general, all products appropriate for the U.S. are stored in the text database.
• It is no longer necessary to restart text workstations after a package swap, because the notification process (for alarm/alert, auto update, and WarnGen auto-display) now saves and restores its list of clients on restart. (This means that the first bug below is much less likely to happen, though still possible for other reasons.)
• Significant-level sounding text, previously stored under cccSIGxxx is now stored under the more traditional cccSGLxxx.
• Mandatory-level sounding data are now available. Previously, the only ones of these stored were in MANAWN.
• The Alarm bell now pops up where last positioned by the user, rather than always in the upper-left corner.

SBN Retransmission

Once the retransmission has been received by the NCF, the range of missing NWSTG data will be retransmitted over the SBN to every site. The site responsible for the retransmission request will ingest the products as a "SAVE DUPLICATE." Other sites which already have this data will discard the data as a duplicate product. There are times, however, when products will arrive at a site that did not issue the retransmission message and they will be processed as first time products. This will occur when a certain time limit has been met and their shared memory table has "rolled over." This is currently under analysis.

The number of retransmitted products depends on the missing range of products. For example, if a site issued a retransmitted message with 21 missing numbers, all of those will be retransmitted. If, however, a site issues a retransmission message with a number greater than 500, 500 of those products will be returned, and in addition to that, a variable number of products. That depends on how much processing time is left at the time of the transaction. So, a site could, if issuing a retransmission message for 600 missing numbers, actually receive 515 back.

Retransmission messages are not issued for problems such as power failures or reboots and functions in a failed-over configuration. A DR has been issued (DR 1463) with regards to a failover problem. This problem occurs only when there is already a process and read number for link 1 on cpsbn2. The new failover would bring a new process number and could produce a missing range of thousands of numbers. A previous failover would have left these older numbers. The following is a workaround when failing over the NWSTG cpsbn:

1. Disable SBN Retransmission on cpsbn2-<site>. From a UNIX window, log into cpsbn2-<site> as root and enter: acq_ctl -c48 -k1 -id. This will disable SBN retrans on link 1.
2. Failover the cpsbn using option 2 from /awips/ops/bin/CP_Reconfigure.
3. A retransmission message will be generated; however, since the interface is disabled, the message will not be transmitted over the WAN.
4. Enable SBN Retransmission on cpsbn2-<site> for link 1 (NWSTG). From a UNIX window, log into cpsbn2-<site> as root and enter: acq_ctl -c48 -k1 -ie. This will enable the SBN retrans on link 1.

D2D/XTerm

Printing

Window Expansions

Green Times

Crash/Hang

Problem: Loading of MRF Mean RH from UpperAir Model Graphics causes the screen to "freeze". DR 622

Problem: Using the Load Mode of Inventory and the 1min lightning from SURFACE causes the screen to "hang" DR 619

Problem: Replacing one of a displayed combined satellite image with another satellite image, with the slide bar on the image control dialog window all the way to the right can crash the pane. DR 706

Problem: Force loading a 4-panel ETA family onto a 4-panel Satellite with the load next image button toggled on causes the large pane to crash and restart. DR 741

Problem: Loading a RUC 850mb PotVorticity (image) crashes the large pane. DR 825

Problem: Displaying the Interstate highways map at infinite density crashes the large pane.

Tools

Problem: The Put Home Cursor is not registering correctly. Cities are showing up in the wrong counties and in some cases in the wrong states. DR 1171

Problem: The Distance Speed storm centroid spped track kinks when the product auto-updates. DR 1057

Zooming/Roaming/Cursor/Looping/Toggling

Problem: Product Loops will run backwards after an automatic restart of a crashed D2D pane. DR 583

Problem: Certain Product loops of numerous surface-based NCEP products listed under the Surface pull-down menu in the NCEP Graphics cascading menus are showing a green time older than the current product time. If the loop is run for an extended period of time, the looping times will show the older green time vs the current product time. DR 595

Color Curve

Map Features/Legends/Menu/Clearing Pane

Problem: Certain Map features do not overlay on the map background correctly. The Map background selections State/County Boundaries and State Boundaries do not line up perfectly, as well as counties and forecast zones. DR 584

Problem: Load Mode does not return to the default value after a pane Clear DR 728

Problem: On the WFO map scale at FWR, there is a 200 mi diameter circular area devoid of cities except for Dallas, Ft. Worth, and Victoria. DR 1214

4-panel

Problem: The Map Background disappears in three of the four panels DR 610

Pane Swapping/Product Replacement

Problem: Date/time group in lower right corner of the four small monitor panes remains even after clearing the pane DR 520

ICWF

Problem: 5% POPs not uploading from grids to stations DR 1417

Problem: HI and WC are not working withing RDF. DR 1149

Problem: Failure to transmit GRIB over AFOS DR 1301

Problem: Trailing POP statement dropped from zone forecast DR 1302

Problem: If the follow option (include UCCs) is set on the CCF and the issue pd amend or correct, the program which places the headers on the product fails. DR 1147

Problem: IGR Data corruption when using local effects and full matrix. DR 1098

Problem: The Text window within IGR does not update correctly once the user has switched the options ->word to 6hr. DR 910

Hydrology

HydroView

System

Message Handling

Process/Product Monitoring

Problem: Data Monitoring does not monitor more than one radar DR 1286

Problem: Product Monitor indicates missing data when it is available. DR 1470

Printing

Radar System

Problem: SIMPACT connection to NEXRAD has a "noisy" status DR 617

Problem: PingFreeway needs to log the status of a SIMPACT reboot DR 682
NOTE: Simpact status messages will now appaer in the radar status menu in the D2D.

Problem: SocketConnection.C problems with radar processes This problem frequently caused line disconnects/reconnects DR 679

Problem: When the NEXRAD acquisition line disconnects/reconnects the site's default RPS List is issued. This default list does not reflect changes made to the site's current RPS list. DR 1105

Problem: Move radarServer to ds1 DR 1095

Site Specific System

Problem: When selecting cities from the D2D Map menu on KRF, only cities around KEAX appeared. Nearly 75% of the RFC area was blank. DR 878

FWR

Problem: FWR-mainConfig.cfg is wrong DR 1207

VUY

Problem: The radar KRMX was moved and renamed KTYX. The OSF radarsInUse.txt file for VUY contains KTYX but this is not a recognized radar by the 3.0 and 3.1 software. DR 1379

System Process/Log

Problem: The WarnGen processes do not always close when the user logs out of the workstation DR 1197

Problem: TextDB Reader dies with a Segmentation Violation due to a truncated product DR 976

Text Alarms

Problem: Occasionally, Alarm Alerts will remain on the screen for up to 20 minutes AFTER the alarm has been acknowledged. Trouble Ticket 19.161 DR 1326

Data

NCEP Graphic

Problem: NCEP Radar legends are displaying erroneous lines plotted across the width of the display in the Radar Legends Surface product. DR 594

Site Specific Data

Problem: At the Regional scale, image registration is off 12-15 miles over the Baja Peninsula DR 1213

ICT

Problem: Station KGBD is plotted in the wrong place on ICT's map DR 1267

TAR

Problem: Satellite image not registered properly on Regional Map. Trouble Ticket 18.836 DR 1382

Text Products

Text Editor/Browser

Problem: The CANCEL button in Text Editor should not cancel out the session unless the operator is prompted via a confirmation message. Trouble Ticket 19.288 DR 1262

Problem: In site-generated forecasts, the text window is not accepting the (tab) correctly. Trouble Ticket 18.962 DR 1251

Problem: Site-created AFOS aviation messages are being incorrectly formatted during transmission. Trouble Ticket 18.648 DR 1250

Problem: The time is sometimes incorrectly displayed in the text browser on the text workstation for the products. DR 596

Problem: 3-character station IDs.
The text subsystem still uses 3-character station IDs. As a result, the Help function in the browser and the button-2 popup station ID info on METAR messages have some problems. In the former, the trailing three characters are used, and some lower-48 sites are identified as Alaskan, and vice versa. In the latter, 4 characters are used only for Kxxx sites. Others use just the first 3, so Pxxx IDs are not found or are incorrect.

WarnGen

Problem: Selecting multiple optional flooding phrases results in a successive sentence fragment. DR 1075

Problem: The Severe High Wind Warning is missing the date in the text. DR 1074

Problem: Cities are not coming up in products generated in WarnGen. Only the county names are being returned. Where cities should be, counties are displayed. DR 1089

Problem: The storm track line kinks upon auto update. DR 1066

Product Maker

Problem: Products and Labels disappeared while using Product Maker DR 562

Problem: Geostrophic and ageostrophic winds are calculated incorrectly in the Product Maker. DR1519, 1520

UpperAir

Problem: The menu item needs to be changed to Springfield, MO (SGF), to reflect the correct location of the site. DR 666

Problem: Selecting a sounding from UpperAir and an Interactive Skew-T and comparing the computed data in two separate Info boxes will show differences in values that should be the same. DR 705

Problem: UpperAir RAOB products being stored multiple times DR 710

Problem: RAOB Plot not plotting all stations DR 876

Surface

Problem: METAR precip does not sum up correctly. Three (3) vs six (6) hour precip was not handled correctly and it was being assumed that one hour precip would only be reported once during the hour when in fact it can be reported many times. DR 636

Grids

Problem: There is one misplaced division in the GridSliceAccessor that breaks the Add function in many cases. DR 634

Radar Products

Problem: Inconsistencies between the radar display and the OTR menu. Add radar cross section products to the menu. DR 566

D2D/XTerm

Crash/Hang problems

• Problem: D2D will hang when loading a radar product at a scale it is not viewable in. DR 1551
  Loading a radar product on a scale that the radar site is not in, will cause the D2D to hang and force an exit/restart of the D2D.

  Workaround: Do not display radar data that is not in the radar area of display.

• Problem: IGC will crash when editing DR 1289/1291
  The IGC will crash when the user is editing an editable element that an extension wants to delete. An example: Displaying Skew-T data in "edit" mode will sometimes crash the large pane, when there isn't any data to edit.

  Workaround: None. The crash seemed to only occur when data for that skew-t was not available. The user does not know if there is data to edit or not and when following the dr scenario, will crash the pane.

• Problem: Inventory for Time Series - Large Pane Crash DR 1292
  Trying to select a Time Series product from the inventory list will cause the large pane to crash.

  Workaround: When displaying a Time Series product, do not select from the inventory.

• Problem: D2D hangs when calling up 1000-500 MRF Thickness product DR 1443
  The D2D will occasionally hang when the user displays the following product: Upper Air menu > Models > MRF 1000-500 Thickness.

  Workaround: Use the MRF model family.

Tool Problems

• Problem: Inconsistency in City Names/City Name Abbreviations DR 1195
  City names that end in "Spring", e.g., Silver Spring, MD, Roaring Spring, PA., are abbreviated as "Spg", e.g., Silver Spg and Roaring Spg. This may cause problems when the user tries to find such locations with the Put Home Cursor application.

  Workaround: CitiesInfo.txt contains the default abbreviations from the Census Bureau data. Sites will edit their files locally to match their needs. Sites will then provide the updated files back to Dave Vercelli of NWSH, who will cut out the CWA piece and put it back into the baseline CitiesInfo.txt file.

• Problem: Put Home Cursor Default DR 1233
  When Put Home Cursor is called up for the first time, the default location is reading KBJC (Boulder).

  Workaround: Enter the location of a desired site.

• Problem: Put Home Cursor dialog box does not function on the display after decreasing frame count of a loop DR 60
  With a loop of any product loaded, under Tools enable Home. Open the Put Home Cursor Box. You can move the position of the cursor by typing information in the box. However, if you decrease the frame count number you are no longer able to move the home cursor by typing in the dialog box. The station ID city name and lat/lon information change but the location of the home cursor on the screen remains unchanged.

  Workaround: The box will not function properly again until you clear the screen. You can still drag the home position with the mouse cursor through to move it.

• Problem: Sampling Problem DR 1407
  It is not possible to edit any of the Tools functions (i.e., baselines, points, home cursor) if sampling is toggled on. The menu will continue to indicate that the products are still editable.

  Workaround: The menu can be selected using mouse button three (3) in the large pane; or turn off sampling.

• Problem: Samples on skew-T charts include a degree sign in front of K.

• Problem: If you turn lat/lon readout on, then bring up a skew-T and sample it, you'll get lat/lon info for the previously displayed map (in addition to the chart information that you want). The pop-up correctly does not include the lat/lon toggle button, so you can't turn it off.

  Workaround: Turn off lat/lon readout before displaying skew-T.

Zooming/Roaming/Cursor/Looping/Toggling Problems

• Problem: Arrow Key Looping DR 1313
  Load a satellite product, bring up the loop properties dialog box, push the down arrow on keypad and the image begins to loop with a forward speed of 8. Push the down arrow until the Forward Speed is at 0 and the looping stops. Now push the down arrow on keypad again; the image begins to loop first forward, then backwards, even with both speeds set at 0.

  Workaround: Push the up arrow again to get back to forward-only looping.

• Problem: Contours can disappear when roaming at high zoom levels DR 822
  Viewing contour products with tight gradients on small scales and zooming to the highest zoom level over an area of the contour product where there is a tight gradient, will at times cause the contours to stop increasing in number through progressive disclosure; instead gaps will form where contours are dropping out.

  Workaround: When this occurs, zoom out to retrieve all of the product contours.

• Problem: Toggling Combined Images Problem DR 749
  Combine any two images. Toggle both images off simultaneously by clicking on the "+" sign in the legends. Next click on one of the two product legends. That product is supposed to toggle back on, but about half the time, it does not and the screen remains blank.

  Workaround: Click a second time to display the desired results.

• Problem: Window/Cursor Error DR 582
  When moving the cursor from one window to another (D2D to hydrology), occasionally the window won't recognize the cursor is in the window and some functions cannot be performed.

  Workaround: Move the cursor out of the window and back in. Cursor focus is indicated by the color of the window border.

• Problem: Zooming on Time Series Plot DR 1308
  If zooming in on a time series and/or pan the image, sometimes the time series data extend to the right or left, beyond the y-axes of the graph.

  Workaround: Do not zoom or pan a time series plot.

Color Curves Problems

• Problem: User-created color curve becomes distorted when combining images DR 1298
  Create a new color curve, one that shades the freezing line on surface temperature for example. If combining that image with another image, the newly created curve will become distorted, i.e., the shaded region that before the combination highlighted the freezing line is now shading a different and larger range of temperature on the part of the combined image.

  Workaround: Click Undo and then Redo in the image color editor.

• Problem: User-created color curve gets distorted when overlaying contours DR 1296
  After editing the color curve using the image colors editor, on a display model product, and then overlaying a contour product, the color curve that was just edited may become distorted, with different colors being inserted into the contour intervals that were just edited.

  Workaround: Click Undo and then Redo in the image color editor.

• Problem: Editing "gridded data" Color Curve produces unstable result DR 1294 Loaded an Eta 4-panel family and edited the gridded data color curve so that a purple band appeared around 540 dam. While running the edited color curve, a change in the number of frames or an auto-update seemed to produce a nonsense color curve. The problem also exists for cross sesctions using a gridded data color curve.

  Workaround: Select Undo and then Redo from the Image Colors Editor.

• Problem: Changing brightness while editing colors causes changes to disappear.
  While using the image colors editor, if you adjust the image brightness, your changes will be removed.

  Workaround: Select Undo and then Redo from the Image Colors Editor.

• Problem: Saving of procedures and color curves across the workstations is not constant DR 605
  Color curves created and saved on workstations are not available to all workstations.

  Workaround: When a color curve is created and saved on a workstation, to make it available to other workstations, a 'save' will have to be executed on another workstation for a color curve. When the operator then goes to select a color curve from the list, the color curve created and saved on another workstation will be made available.

Map Features/Legends Problems

• Problem: Metar Legend Problem DR 1119
  Swapping a 4-panel product into a small pane makes the legends unreadable.

  Workaround: To read a product legend, swap the product back into the large pane.

• Problem: Map Legends Problem DR 1303
  The Hide Legends function, invoked on a D2D that only has map features displayed, does not work. When the operator clicks the third mouse button and invokes the Hide Legends, not only will the map feature legend remain displayed, the first mouse button function to hide individual map features will not work. Once the operator clicks the third mouse button again and invokes the Show Map Legends, will the first mouse button capability be restored.

  Workaround: Select Show Map Legends from the third mouse button pop-up menu, which allows the first mouse button function to hide individual map features to work.

• Problem: Map background error DR 1161
  State boundaries selected from the Maps menu does not recognize Washington DC as being a separate entity from Virginia and Maryland.

  Workaround: None

• Problem: Warning Locations at an RFC DR 1133
  The Map Feature, Warning Locations, is available at an RFC; however, when selected, the legend is updated with Warning Locations, but nothing is displayed in the map.

  Workaround: None. RFC's do not issue warnings.

• Problem: Load mode of Inventory and Set Time Resolution DR 732
  When trying to load map features onto the D2D display, if the load mode is set to Inventory or Set Time Resolution, only an Inventory box or Set Time Resolution box will be displayed, instead of the map feature on the display.

  Workaround: Never set the D2D load mode to Inventory or Set Time Resolution when trying to load map features onto a D2D display.

• Problem: Map background - Manassas, VA DR 1288
  The independent city of Manassas, VA is displayed at all map scales and on all relevant map backgrounds, even without zooming in. No other independent city in Virginia is displayed in this manner.

  Workaround: This is due to the setting of the progressive disclosure in the CitiesInfo.txt. Sites may edit this file.

• Problem: Map Background RFC Drainage Basin DR 1330
  Map background rfc boundary drainage basin is missing.

  Workaround: None

4-Panel Problems

• Problem: 4-panel mode is disabled only by clearing the screen.
  Once you're in 4-panel mode, you stay there until explicitly clearing the screen. If you select products on a different scale, you'll get the same thing loaded in each panel.

  Workaround: Clear the screen to exit 4-panel mode.

• Problem: Lost Data DR 1118
  Bringing up a single pane layout from a 4-panel AVN product, then back to a 4-panel display results in three of the four panels being empty.

  Workaround: If all four panels of data are desired, do not select Single Panel Layout from a 4-panel display.

• Problem: Red Banner Message Error DR 1422
  When a 4-panel radar image is loaded from a History List, any red banner messages for missing data are not displayed.

  Workaround: None. Red banner messages are not available for products loaded from a History List.

• Problem: Loading a 4-panel from inventory error DR 739
  The loading of a 4-panel satellite 18Z product, selecting Combine next image from the Image Menu in the Controls menu, then loading a 4-panel Eta from Inventory mode at the same time (12z run, 6hr) causes the D2D to crash.

  Workaround: Do not load the two above products in the manner described.

• Problem: 4 Panel Satellite crash DR 714
  If a 4 panel satellite product is loaded in the large pane, the Load Mode is set to 'forced load' and combine next image is toggled off in the control image panel, if another satellite image is loaded, the 4 panel large pane crashes.

  Workaround: Be sure to have Combine Next Image toggled to the "on" position.

• Problem: AVN/ETA intermittent lockup on D2D DR 1269
  The AVN/Eta will periodially lockup the D2D on the last time step that is being displayed during the time the AVN/Eta new model runs are coming in.

  Workaround: Load the AVN/Eta run into a pane on another D2D.

Hydrology D2D/Xterm problems

• Problem: Motif close - Stage III from D2D DR 1130
  Launching Stage III from D2D and closing it through the motif does not exit the application from the workstation; thereby, preventing another Stage III application launch from the D2D.

  Workaround: Close the application from the Stage III panel. If the operator exits from the D2D, close out the D2D and open another D2D.

• Problem: IFP/Stage III - Xterm DR 1131
  When either Stage III or IFP is launched from an x-term, the application dies with the following error:

  Xerror of failed request:BadName (named color or font does not exist)
Major opcode of failed request: 45(x-OpenFont)

  Workaround: Open IFP and Stage III from either the mouse on the graphic workstation or from the D2D.

Radar D2D problems

• Problem: V-R Shear Error - Large Pane crash DR 1306
  When moving the V-R Shear product rapidly around over a Velocity radar product, the large pane may crash and restart.

  Workaround: None

Pane Swapping problems

• Problem: Small pane swapping sometimes becomes blank during swap DR 545
  Sometimes swapping a panel with a product into the smaller pane causes the pane to become blank.

  Workaround: Swap the small pane back into the large pane to redisplay product; or zoom.

• Problem: Skipping the last frame of a loop will result in a blank pane DR 593
  Using the mouse button three (3), skipping the last frame of a loop of any product, without turning looping back and then swapping the product to another pane will result in a blank pane.

  Workaround: If the last frame is skipped in the loop, turn the looping button BACK ON, before swapping to a small pane.

• Problem: Pane swapping with editable products DR 1425
  With certain (editable) products, such as home cursor, alert editor, and the WarnGen centroid, swapping them from small panes can be a problem. For example: Home cursor - swapping an editable Home cursor and clicking on the third mouse button relocates the Home Cursor to that point; AlertArea Editor and WarnGen panes - new warning areas and alert cells are selected erroneously when clicking on mouse button three (3).

  Workaround: Do not swap panes with (editable) products; or, hold down the right mouse button in the small pane until swap unload pop-up appears, then swap small pane with the large pane.

IFPS

IFPS Tip Sheet --

• efpc_const.ccc

  This file was updated in build 4.0. During the installization process, this file will be copied to efpc_const.ccc.old and the new file installed where ccc is the 3-letter site identification. Please modify the new file to include any site customization.

• Unloading 5% POPs from grids to stations

  Currently, the environmental variable PUB_PRND equals 5 or 10. If your site wishes to unload 5% POPs for the CCF set this variable to 99. Note, that this change will unload 5% POPs for both stations and zones DFMs. If the site only wishes to have 5% POPs for station, you will have to create a new environmental variable (within icwf-ccc.env) called PUB_PRND_STN and it should equal 99 while PUB_PRND stays at 5 or 10. Do not forget to add PUB_PRND_STN to the export line included in this section within the icwf-ccc.env. Once the environmental variable has been created, the FP will have to modify the upd_stn_frm_grd.bat changed PUB_PRND to PUB_PRND_STN.

• Problem: ICWF Problems - Zones DR 1504
  There are times when "Zones" is selected from the ICWF Master Menu and an error window is displayed: "Fatal Error - Can't get combo maps window to appear".

  Workaround: None

• Problem: ICWF - Delete Right/Delete Left and surface products DR 1059
  Delete Right/Delete Left and surface products: Within the Aviation Editor, the delete left/delete right tools are active on the cloud deck. If the forecaster attempts to delete left/delete right a particular cloud deck by clicking on another icon (i.e., precipitation, fog, etc.) the application will hang.

  Work around: Make sure modifications are done on the cloud icons

• Problem: ICWF - Terminals DR 1058
  IFPS - Terminals: Within the Aviation Editor, the modification tool is active on the cloud deck. If the forecaster attempts to modify a particular cloud deck by clicking on another icon (i.e., precipitation, fog, etc.) the application will crash.

  Work around: Make sure modifications are done on the cloud icons

• Problem: Incorrect weather order in TAF DR 809
  Incorrect weather order in TAF: The order of the weather forecasts is incorrect occasionally.

  Work around: Post-edit the product correcting the weather order

• Problem: GMOD icons clipped DR 987
  GMOD icons clipped: On the X-term, the GMOD tools are clipped in the upper right hand corner once they are selected and moved over the drawing area. This appearance does not affect the tool functions.

  Work around: None.

• Problem: Converting present weather codes DR 988
  Converting present weather codes: This problem relates to the decoding of metar observations. Some of the problems observed: Some present weather codes not handled correctly (i.e., if the decoder does not "understand" a present weather code it sets it to missing); decode will allow dewpoint > temperature; decoder is using the temperature/dewpoints found in the message, not the remarks; and vertical visibility set to missing.

  Work around: The impact of this DR is on the quality of the LAMP forecasts. LAMP forecasts will be produced regardless of the decoding of the observations.

• Problem: Early/Extended Forecaster - data overwriting DR 999
  Early/Extended Forecaster -- data overwriting: When the early & extended forecaster have performed grid modifications at the same time and have exited TIS, the unloading process results in the overwriting of data. The forecaster which exits last will have his/her changes unloaded. The other data seems to have reverted to the original guidance. Need a locking mechanism on the gridded data.

  Work around: Each forecaster modifies the grids independently.

• Problem: ICWF Forecast Text DR 1427
  The forecast text window from the Interactive Guidance Revisor has a much larger font than in the past. The small font is so large that it doesn't fit in the window if the forecast is more than a few words.

  Workaround: The operator must use the scroll bar to read the entire text.

• Problem: ICWF - ZONES DR 1060
  IFPS - ZONES: The error message, "An error has occurred during the formatting process," results in the following conditions: 40 or less temperatures; 30 or more mph wind; blowing snow obvis; and no precipitation. Note: Unable to repeat with the information provided in the DR.

  Work around: None.

• Problem: Storing of a large county name within IFPS DR 1337
  The current zone_directory table within the IFPS database will not support a particular zone name. This zone name is greater than 40 characters which is the limit of IFPS zone names.

  Workaround: None

• Problem: Mod_climo does not have necessary data DR 857
  Mod_climo requires coop data which has not been provided.

  Workaround: None

• Problem: hpterm is the wrong size DR 930
  IFPS: hpterm wrong size: One the workstations, the hpterm which displays the formatted products is the wrong size. This results in the text being misaligned.

  Work around: Either use the text workstation or re-size the hpterm on the workstation.

• Problem: Missing pup01 and cld grids in MOS row DR 968
  Several projection in the clouds and precip prob are missing within the slider application. These missing thresholds are denoted by no data and dimmed sliders. The actual data is missing from the MOS row.

  Workaround: None

• Problem: Adjusting dewpoints from missing data DR 1000
  Adjusting dewpoints from missing data: Within IGR, when the forecaster sets a missing 3-hourly temperature data to the correct value and then proceeds to adjust a missing dewpoint value. The first increment of the dewpoint results in 50 degrees and any modifications from there will make the temperature data equal to the adjusted dewpoint data. This error only occurs if the forecasted temperature data is below 50 degrees.

  Work around: Set the dewpoint data first.

• Problem: ICWF County Name DR 1134
  The following county is misspelled in ICWF: Woodspm. It should read: Woodson

  Workaround: Change the zone/county name in the geography_directory table located in icwf_ccc database

• Problem: Switchable 6-hr pds DR 1148
  The capability to alway have two 6-hr pds causes the ZFP to not work.

  Workaround: Use 12-hour periods except on updates where a single 6-hour period will work.

Site Specific IFPS problems

Workaround: None

Hydrology

HydroBase

• Problem: Help button doesn't work DR 1320

  Workaround: Use manual.

HydroView

• Problem: Help button doesn't work DR 1320

  Workaround: Use manual.

• Problem: Status Forecast Error DR 586
  When hydroview is started, occasionally the map will come up blank with a blob of forecast points in the upper left hand corner.

  Workaround: Zooming out and then back fixes the problem.

• Problem: Hydroview Time Series Error DR 599
  When displaying precipitation time series for time periods greater than a year, instead of discrete bars representing hourly precipitation amounts, a solid bar of red or yellow displays which covers multiple months. This does not occur for time series lengths of a few months but does occur for lengths of a year and greater.

  Workaround: None

RiverPro

• Problem: Help button doesn't work DR 1320

  Workaround: Use manual.

• Problem: Extra characters when viewing saved and issued products DR 915
  Using RiverPro's editor, create and save a product, then issue the product. When viewed using the Previous Product Information window there are extra characters at the end of the message. When the same product is viewed using the editor (edit), the characters are not present.

  Workaround: None

• Problem: Spelling error in RiverPro DR 1093
  CARDRIVE Template in the Call-to-Action Template has a misspelled word.
  'Do not drive thruough flooded areas.'
  Workaround: For existing sites, the fix is to simply edit the cta.tpl file in the /awips/hydroapps/whfs/local/data/app/riverpro directory, in order to correct the misspelled word. This version of the release notes serves as the fix.
  Note: For new sites, version 4.1 will contain an updated cta.tpl file with the correct spelling of the word. We do not want to place a new cta.tpl file at existing sites, as this will overwrite the existing cta.tpl file and any site-added templates will be lost.

System

Localization/Time Zone Problems

• Problem: Time Zone handled incorrectly DR 1539
  When a site configures to a time zone other their own, the default east coast time zone is automatically returned.

  Workaround: None.

• Problem: portInfo.txt/pupId.txt files not being restored DR 1399
  After running mainScript.csh, the portInfo.txt and pupId.txt files were being written over with the default files.

  Workaround: Before running mainScript.csh, run, as root: /awips/opa/bin/radar_files backup and /awips/opa/bin/radar_files restore after the mainScript.csh has been run.

Message Handling Problems

• Problem: Text workstation windows 2/3/4 not writing to logs DR 1391
  Only text workstation window one (1) will write to the local display log. If an operator sends out text products from Text Window 2, 3, or 4, on the text workstation, the display log will not write any entries such as: PRODUCT sent to AFOS, PRODUCT written to db, PRODUCT sent to MhsServer, or any error condition log entries.

  Workaround: This does not preclude the message from being transmitted; however, log entry traceability is lost on text windows 2, 3, and 4.

• Problem: Text window from D2D does not log entries in the display log DR 1392
  The D2D text window is not logging any entries into the workstation display log.

  Workaround: This does not preclude the message from being transmitted; however, log entry traceability is lost on messages transmitted from this text window.

Product Monitoring Problems

• Problem: Product Monitor indicates missing data when it is available DR 1470
  Lightning data indicated a red X for late products in the Product Monitor although they were available and updating.

  Workaround: Inventory lightning to check data.

• Problem: Data Monitor Radar Velocity is not always available DR 1334
  The "Base Velocity (V) elev0_5 res1" may not be available all the time and may not warrant a warning to the NCF.

  Workaround: None

Printing Problems

• Problem: Browse button in print window works only the first time DR 1566
  Once the browse button to print a file has been used, the operator will not be able to use the browse button again, for the life of the D2D.

  Workaround: The full path and filename can be entered by the operator and then printed.

• Problem: Plots not printing to displayed magnification DR 1013
  If a user modfies a plot magnification and then tries to print it as is, the new magnification is not printed.

  Workaround: Print with options and adjust the magnification/density in the print with options GUI.

• Problem: Distance Bearing overlay not printing DR 1109
  A Distance Bearing overlay will not print.

  Workaround: None

• Problem: Printers not recognizing contour style DR 1204
  Printers don't recognize contour styles specified on the screen by the user.

  Workaround: None

• Problem: Printing zoomed levels of contours DR 1220
  Printing zoomed levels of Model data does not capture the same contours that appear in the D2D.

  Workaround: None

• Problem: Cannot print NCEP graphics (SPC watches, etc.) DR 1378
  SPC Watches will not print.

  Workaround: None

• Problem: Printing modified lines on model displays DR 601
  When changing a solid line to a dashed line on a model display and printing it, the line is printed as a solid line.

  Workaround: None

• Problem: Printing a 4-panel model display DR 602
  4-panel displays cannot be printed.

  Workaround: Print model data from a single pane display

Radar system problems

• Problem: DialRadar server consumes considerable resources when multiple dial radars are in use. DR 1547
  When a large number (10-12) of dial-up radars are used by a site, the system slows down considerably. When two or three dial-up radars are used from a workstation, this is not a problem.

  Workaround: A site should only use two to six dial-up radars at a time.

• Problem: Inaccurate Message in RadarMessageHandler log DR 1550
  If a workstation is rebooted before the D2D is closed, the RadarMessageHandler process will start recording SocketConnection.C errors. There is no operational impact.

  Workaround: Exit all D2Ds on the workstation prior to rebooting.

• Problem: restartRadar does not work for ports on the second board DR 1318
  restartRadar uses only the first field of portInfo.txt. This fails for simpact port 4 since it is represented by 0 1 in portInfo.txt

• Problem: PingFreeway needs to detect dead socket on TCP_IP when analog line disconnects DR 677
  When the analog line has a disconnect, pingfreeway needs to be able to detect a dead socket on the TCP_IP. No status was returned once the line was disconnected; however, upon reconnection, the SIMPACT went into a "hang" state.

  Workaround: If there is an analog line disconnect, icpReset needs to be run on the SIMPACT board with the active NEXRAD port, e.g., icpReset0 from the data server running the dsswap package.

• Problem: Radar status messages DR 1469
  Need to reduce the number of radar status messages that appear in the radar status bar in the D2D.

  Workaround: None

• Problem: Behavior of a lost connection followed by cs_unbind is unpredictable. DR678
  The behavior of a lost connection followed by a cs_unbind is unpredictable. The fix needs to handle the condition causing DTTs. This error is displayed in the wfoApi log on ds1- in the current day log directory.

  Workaround: Run x25_restart# on ds1-<site>. # = NEXRAD line port number.

• Problem: DialOut Radar - Runaway phantom processes DR 979
  Numerous send requests on DialOut radar without receiving a disconnet from the previous send, can periodically cause the DialOut radar process to become a 'phantom' runaway process. This has at times caused some performance issues on the primary data server.

  Workaround: By reviewing the Radar Status Window on the D2D, ensure a clean disconnect is received BEFORE issuing another DialOut radar send.

• Problem: Creating an RPS list with too many products does not give an adequate error message. DR 1526
  If an RPS List is sent out with more than the required amount (9.6 = 20 products, 56 k = 50 products), the error, 'radarsite: RPS List not sent' is displayed in the Radar Status Message window. The error is not sufficiently identifying the problem.

  Workaround: Ensure only a maximum of 20 products are sent in an RPS List on 9.6 NEXRAD comm lines and a maximum of 50 are products are sent in an RPS List for a 56kb NEXRAD comm line.

• Problem: Checking radar status results in MainPane restart DR 1194
  Loading a 4-panel combined radar image, zooming 2x and then attempting to load the radar (NEXRAD) unit status graphic causes the main pane to restart.

  Workaround: Do not load the NEXRAD unit status graphic with a 4-panel combined radar image.

Radar system file Problems

• Problem: radarsInUse.txt file cannot support the option 2 DR 933
  The radarsInUse.txt file does not support the option 2 functionality; whereby, the operator can configure a NEXRAD line to be BOTH dial-out and dedicated.

  Workaround: Configure a NEXRAD line to be EITHER dedicated OR dial-out.

Decoder system problems

• Problem: Decoders crashing due to invalid products:
  GribDecoder - invalid products DR 1132
  MetarDecoder crash DR 1474
  Invalid products cause the decoders to segment and crash. If capable they will restart, if not they will "hang".

  Workaround: If the decoder has run out of "starts", then restart the process manually. If, multiple invalid products are bombarding the system, the /data/fxa/Grid/SBN directory must be deleted and recreated.

ICWF system problems

• Problem: Straight Line GMOD hanging DR 1172
  In the Grid Modification window, drawing a straight line acorss the grid free border, going down into the grid and loop the contour back up towards the straight line will cause the window to lock up and crash, leaving the whole IFPS application locked.

  Workaround: Do not perform the above function.

• Problem: Text Workstation - IFPS DR 1056
  Launching IFPS from the mouse on a Text Workstation and then exiting, creates an error condition, whereby using any of the text windows, browsers, etc., returns an error:
  Error:Xserver insecure (must use xauth - style authorization); command ignored.

  Workaround: If launching IFPS from the Text Workstation, the operator must log out and back in to successfully use other functionalities.

• Problem: Sizing Full Matrix windows - IFPS DR 1183
  Moving or attempting to size a full matrix window, will result in the loss of Mx 2-3 boxes. The window cannot be re-sized to retrieve the row of Mx2-3 matrix boxes.

  Workaround: Close the Full matrix window and re-open it.

Site Specific System Problems

Puerto Rico Sites
• Problem: Localization - Puerto Rico Sites DR
  Localization is not available for Puerto Rico AWIPS sites.

  Workaround: None

  SLC

• Problem: SLCSGLSLC and SLCMANSLC are not in the text database DR 940
  Workaround: None

  TAR

• Problem: AFOS - Text messages created in AWIPS DR 1192
  Boston is seeing some corruption in the text messages being generated and sent from AWIPS, when they are received from AFOS.

  Workaround: None

System Process/log problems

• Problem: Decoder log messages DR 1304
  There are notices in the decoder logs that claim the decoder has not processed a message for periods of time; the log clearly shows in some cases that is not true.

  Workaround: None

• Problem: TextDB Reader hang DR 1402
  Loading text messages from the Load Cmd in the text window with -1product will cause the textdb reader to hang and consume an enormous amount of cpu time.

  Workaround: When requesting a previous version of the product type in -1:, OR request it from the menu bar.

• Problem: The following are log-breaking-at-new-day problems:
  DR 1397 - afoscommsrv log
  DR 1411 - GribDecoder
  DR 1485 - MhsServer
  DR 1412 - RadarServer
  This problem does not allow scour to remove the 'date' log directories older than 2 days as designed.

  Workaround: With the exception of the afoscommsrv.log, the log will break when activity is being written to the log; however, it could be hours before that condition is met. To manually break the log, the process would have to be taken down and restarted. This will create a new-day log in the current day directory.

• Problem: MhsServer.log DR 1352
  The following error is being displayed in the MhsServer.log: Connection.C Problem Warning: this process using target MHS_SERVER might be running on the wrong host. It is not known why this error is being returned, or if it is causing some serious software malfunction.

  Workaround: None

Text Alarms Problems

• Problem: Text Alarm/Alert Products - cannot tell workstation/site default entries from editable entries DR 882
  The System Manger may add workstation/site default alarm/alert products; however, there is no visual way for the user to know that default entries exist in the Text Alarm/Alert Products List.

  Workaround: None. If the user tries to modify one of these entries, a message is displayed at the bottom of the dialog box.

Database Problems

• Problem: Incorrect paths for data table in fxatext.sql DR 1560
  The fxatext.sql script in /awips/fxa/informix has incorrect paths for the data files to load into the fxa database when the database needs to be created or recreated. The path for stateMatch.dat and largeText.txt are currently set to /usr/local/informix. The path for versions lookup table is also incorrect. It is set to /usr/local/fxa/data/localizationDataSets/FSL.

  Workaround: The correct path for stateMatch.dat and largeText.txt should be:
  /awips/fxa/informix
  The correct path for the versions lookup table should be:
  /awips/fxa/data/localizationDataSets/<site>

Data

NCEP Graphic problems

• Problem: NCEP Graphics: UpperAir Model Graphics Product Error DR 707
  Bad MRF MeanRH and AVN 850-500 Thickness data caused the UKMO, ECMWF, and S-blend 6-10 500 height products to be centered over Africa when they should appear over the pole.

  Workaround: None

• Problem: NCEP Upper Air Plots not displayed until zoom DR 1281
  On the North American scale, most of the upper air reporting station plots are not displayed at the full (zoomed out) scale for the NCEP upper air plots.

  Workaround: Non-functioning RAOB sites were cleaned up and deleted, reducing this problem. All RAOBs not being plotted at the NA map scale is a progressive disclosure problem.

• Problem: NCEP Redbook Graphic Radar Summary Label "Spiking" DR 1428
  NCEP Redbook Graphic (RBG) Radar Summary Label "Spiking" - The radar summary label overlay will occasionally produce a "spike" off of the echo height label. "Spike" is generally about two inches in the direction of 020 degrees.

  Workaround: None

• Problem: NCEP Graphics Surface Obs - small registration problems DR 1434
  Plotted data on NCEP Daily Precip, Snow Cover, and Max/Min Temp (Surface:Surface Obs) products do not correspond with their METAR station locations. An example: 6 inches of snow reported over the Great Salt Lake. Also plots around DC did not match up with their METAR stations.

  Workaround: Check AFOS available data.

Site Specific Data problems

Fort Worth
• Problem: Local UpperAir products - Forth Worth Tx DR 1325
  Local UpperAir product is reflecting Midland TX product instead of Fort Worth.

  TAR

• Problem: Goes8 images not registered properly for TAR DR 1226
  Satellite images displayed on the Regional Map are showing a 10 mile 'mis-gridding'.

  Workaround: Temporary fix for 4.0 was to change the corner points where the software thinks the image is.

Text Products Problems

• Problem: MHS cannot handle 4 letter site ids DR 996

  Workaround: None

• Problem: ANCOFFANC is being stored as ANCHSFANC DR 1429
  Anchorage Offshore Forecast is stored in the database under the High Seas Forecast identifier, ANCHSFANC.

  Workaround: Obtain the data from AFOS.

• Problem: Local Text Products DR 1354
  Local text products are being truncated from AFOS to AWIPS.

  Workaround: Add these products to the large text database on the data server via the textdb -l (lower case L) command. This will correct future acquisition of these products.

• Problem: Text products - TWB and TAF DR 1198
  TWB and TAF text products are being truncated too far to the right when received from AFOS into AWIPS. The TAF products are being truncated five spaces to the right and TWB products are being truncated two spaces too far to the right.

  Workaround: None

• Problem: Generating TAF Text products - not being indented DR 1256
  Continuing lines in TAF text products are not being indented properly when generated.

  Workaround: Manually insert proper tabs.

WarnGen Problems

• Problem: WarnGen not working for long-fuse warnings at PHI DR 1458
  PHI CWA currently does not include counties when long-fuse warnings are issued.

  Workaround: When necessary, edit the text manually.

• Problem: WarnGen not handling 2 time zones DR 1466
  BIS county warning area (CWA) covers two (2) time zones. WarnGen is only generating warnings for Central time regardless of county.

  Workaround: None

• Problem: No Marine Warnings in WarnGen DR 1516
  There are no Marine-type warnings available for use in WarnGen.

  Workaround: None

• Problem: Pilot reports problems
  Like many other products, pilot reports come in a collective and are stored under the site id instead of your local CCC. Thus, a pilot report referenced to DHN would be stored as BHMPIRDHN. They can be called up by state using "ss.PIR". Some PiReps erroneously get stored by 2-letter state ID, e.g., PIRAK.

• Problem: A:HH CCCNNN does not work properly.
  A:HH gives you data from HH hours ago, rather than from hour HH.

  Workaround: None.

• Problem: WarnGen Scale Problem DR 1205
  WarnGen vertices do not correctly change to the current scale when changing scales.

  Workaround: Do not change scale.

• Problem: Misspelled Cities DR 1439
  Misspellings were found for Frederick, Charlottesville, and Waynsboro Virginia.

  Workaround: When necessary, edit the text manually.

• Problem: Updates needed to citiesInfo.txt for the Balt/Wash area DR 1341
  The problems noted in MD:
  Two references to BWI
  Friendship Intl Arpt should be removed
  Two references to Glen Dale
  Baltimore Martin St should be listed as "(MTN) Martin St Arpt.

  Workaround: CitiesInfo.txt contains the default abbreviations from the Census Bureau data. Sites will edit their files locally to match their needs. Sites will then provide the updated files back to Dave Vercelli of NWSH, who will cut out the CWA piece and put it back into the baseline.

• Problem: States Not listed in County and Cities List DR 1003
  At WFOs that have a forecast area in two states (i.e., IAD), when the counties and cities are listed in the text message, there is no identification as to which counties or cities are in which state. For example, Frederick is listed twice in a statement because there is a Frederick County in Maryland and in Virginia.

  Workaround: When necessary, edit the text manually.

• Problem: Manassas Park shown in Warning Box but not included in created text DR 1247
  Manassas Park was part of the Warning Box for a Blizzard Warning, but was not part of the created text.

  Workaround: When necessary, edit the text manually.

• Problem: WarnGen still lists independent VA cities as counties in some WarnGen products DR 1394
  Severe High Wind Warning, Flash Flood Watches, and Flood Warnings show the independent cities of Virginia as counties. DC is listed as a county in Maryland in Blizzard, Blowing Dust, Blowing Snow, Flood Watch, Dense Fog Advisory, Freeze Warning, and Frost Advisory WarnGen products.

  Workaround: All erroneous text must be manually edited.

• Problem: WarnGen locations in "Other cities list" is inconsistent DR 1339
  When WarnGen creates the warning text, and "Other cities list" is included from the optional bullets menu, the number of cities included is inconsistent. For the same area and warning type, sometimes it lists a large number of cities/towns/etc; sometimes it lists just one or two. There is no pattern to it and it is not easitly repeatable. It has only been seen on the Severe Thunderstorm, Tornado, and Flash Flood Warnings.

  Workaround: None

• Problem: WarnGen blizzard warning default even when another product type is displayed DR 1246
  If a warning or advisory for an "Other" product type is created, and then a Tornado, Flash Flood, or Severe Thunderstorm Warning is created, if you select the Other box without reselecting its parameter, the result will be a Blizzard warning even though that's not the product type shown in the "Other" display box. A Warning was created for product type of the Other category (i.e., dense fog) and then one was created for a Flash Flood, Severe Thunderstorm, or Tornado. When a new warning was attempted for the product still shown in the Other box, the created text was for a Blizzard Warning.

  Workaround: If the conditions of the DR have been met, the displayed product in the Other box will not return to the operator the desired product text. The operator, when generating another type of product, must open the Warnings box again, and reselect the desired product.

• Problem: WarnGen Polygon - line loss DR 803
  In WarnGen, add a vertex to any side of the polygon by clicking mouse button 2 when the cursor is in a cross-hair configuration. To remove the vertex, click mouse button 2 when the cursor changes to a right-pointing arrow. After deleting the vertex, if you click mouse button 2 again while the cursor is still "right-pointing", it will delete half of your box.

  Workaround: If you move the cursor so that it takes on the cross-hair shape before clicking mouse button 2 again, your click will produce the expected result of bringing back the vertex.

• Problem: Independent cities duplicated in created text DR 1385
  The independent cities of Virginia appear twice in the created text for Severe Thunderstorm, Flash Flood, and Tornado warnings. They are appearing in the statement for counties and "Other cities".

  Workaround: The message would have to be manually edited.

• Problem: WarnGen warning box becomes uneditable DR 1338
  On WarnGen, the edit box sometimes becomes uneditable even though the "Edit Box" is on. The open vertices will suddenly change to closed and the box freezes.

  Workaround: Close and restart WarnGen, or, click on the Edit Box radio button (even if it is yellow)

• Problem: WarnGen storm track does not update the forecast part of the track upon auto-updating DR 1273
  With WarnGen, when the underlying image auto-updates, the warngen storm centroid will move forward, but the forecast extension of the storm track does not likewise extend further in time as it did in Build 3.

  Workaround: Close and restart WarnGen.

• Problem: WarnGen (D.C.) Problem DR 1159
  When creating a WarnGen product that uses forecast zones, the District of Columbia appears in the list for the state of Maryland. The products which list the District of Columbia in the State of Maryland are:
  Blowing Snow Advisory, Blowing Dust Advisory, Flood Watch, Dense Fog Advisory, Freeze Warning, Frost Advisory, and Blizzard Warning

  Workaround: Edit the product as required.

Product Maker Problems

• Problem: Product Maker - TwoD Error DR 1309
  Loading a satellite image from the TwoD and contour from the Make Box will produce an "image" even though the Status/Value line will state that a contour is loaded.

  Workaround: None

• Problem: Trigonometric Error in Product Maker DR 1461
  In Product Maker, any values entered in the insert constant box will be assumed to be degrees when selecting sin, cos, and tan. The Product Maker considers the same values in radians when selecting arcsin, arccos, and arctan.

  Workaround: None

• Problem: Venetian blind effect with satellite images out of Product Maker DR 1477
  Frequently, when loading a satellite image out of Product Maker at the WFO scale, the displayed image will take on a venetian blind effect.

  Workaround: None

• Problem: Intermittent error when loading satellite images from Product Maker DR 1476
  Sometimes, when loading a satellite image out of the Product Maker, an error is returned:

  "Error:ncendef:xfr_NC_fill". This seems to occur when the Product Maker has been open for an extended period of time.

  Workaround: Close and restart the Product Maker.

• Problem: Satellite Images loaded out of Product Maker are displayed upside down DR 1475
  On two development sites, loading satellite images from Product Maker produced an "upside down" image.

  Workaround: None

• Problem: Geostrophic Wind Speeds from Product Maker and Volume Browser DR 1519 This DR is also in the Volume Browser section.
  Geostrophic Wind Speeds from Product Maker and Volume Browser don't always match. Wind direction was always the same; however, wind speeds from Product Maker are generally larger than those form the Volume Browser at higher latitudes, and are generally smaller at lower latitude.

  Workaround: None

• Problem: Continued problems with geostrophic winds from Product Maker DR 1520
  Product Maker does not properly compute geostrophic winds for all applicable models at all scales. AVN and MRF at Northern Hemisphere/MRF and NGM at North America at several pressure levels return zero values. MRF at Northern Hemisphere gives a "limit 20" frame error when loading with *_Hr. AVN at North American scale gives "Height is not available for AVN on grid202" error at several pressure levels. All of these products can be correctly loaded from the Volume Browser.

  Workaround: Do not enter the above values in the Product Maker.

• Problem: Theta Error in Product Maker DR 1316
  When loading a pressure product along an isentropic surface (constant theta), an error occurs in which the same pressure is plotted for all theta values below 279K.

  Workaround: None

• Problem: ThreeD - Product Maker display error DR 1312
  Selecting an option from the ThreeD menu, the Source menu, the lat and lon menu, the Pressure menu, and the Time menu will give you the necessary ingredients to get a scalar value. Occasionally, the scalar button in the Make box will not highlight and is not selectable. The only selectable item is Contour and when it is loaded and error is returned:
  Ncdimdef: NC_UNLIMITED size already in use:dimension "record" index(0)

  Workaround: Select a lat/lon value from the menu, load the product, and then select a user specified lat/lon.

• Problem: ProductMaker has a wrong formula of geo-wind on theta level DR 1430
  The computation of geo-wind on isentropic surface is different from the one on pressure levels. The productMaker has a wrong formula of geo-wind on theta level.

  Workaround: The user needs to input the formula manually.

• Problem: Product Maker contour levels error DR 1278
  The Product Maker is not displaying model data at the entered contour levels. In 4.0, a new feature of the Product Maker is the ability to specify the contour interval with which to display model data. The user can input a number for the interval; however, the Product Maker still displays the data at default intervals.

  Workaround: None

• Problem: Unary Log function in Product Maker no longer working DR 735
  If the user selects Height from the ThreeD Field, ETA from Source, 500 mb from Pressure, *_Hr from Time, and chooses log from Unary Functions, selects Load; the Status Line reads: "status/value returned: function is not defined: log10". The same results were returned for other products.

  Workaround: None

• Problem: Product Maker crashes large pane DR 784
  Loading 1/(COS(Abs_Vort[Eta,,,500mb,*])) will crash the large pane and restart the ICG_process. This happens when combining the (1/x) function and the (COS) function from the 'open to box'.

  Workaround: Do not combine the (COS) function with the Abs_vort field.

LAPS Problems

• Problem: Profiler data does not always get into LAPS DR 1537
  Profiler data usually gets into AWIPS around 20 minutes after the hour, which is when LAPS kicks off. One of the first things LAPS does is go looking for the profiler data for that hour in the system. Often, the timing is such that LAPS will to looking for the profiler data before some or any of that data has come in for that hour, thus, the current profiler data will not get into the LAPS run for that hour. The wind portion of LAPS will run without this profiler data, however, those sites that have profilers within their LAPS domain may often miss having this data in a given hour.

  Workaround: None

• Problem: LAPS MSL pressure contour and analysis problems DR 1372
  LAPS is putting Low and High pressure centers together, has put Lows in areas of anticyclonic flow (the real low is south of the LAPS area); there is no continuity. Contours at times seem too smooth and are incorrect compared to the surface METAR data.

  Workaround: None

UpperAir Problems

• Problem: Skew-T Plots without reference maps DR 1473
  The reference map in the upper left corner of the Skew-T plot was missing for the following RAOB sites: 1) In the Western US: Spokane (OTX), Mercury NV (DRA), Miramar NAS CA (NKX), Gila Bend AZ (GBN); 2) In the Central US: N Little Rock AR (1M1); 3)In the Eastern US: Pittsburgh (PIT), Dulles (IAD), Nashville TN (BNA).

  Workaround: None

• Problem: RAOB BUFR Geopot hgt truncated below 500hPa DR 1479
  The RAOB message, in its BUFR format, is truncating the GPH value from the surface up to 500mb. For example, if one observes the height for the Denver station from a 700mb plot in D2D, then the height is displayed as "060" and interpreted as 3060 meters. The text version of this displays the 700mb height as 3066 meters.

  Workaround: None

• Problem: RAOB received with invalid timestamp DR 758
  Erroneous time-stamped product DR 846
  Periodically, products are being received with 2038/1970/2004/1934 year-mark times. These are being stored in AWIPS with those timestamps.

  Workaround: None

• Problem: Interactive Skew-T (IST) DR 1106
  While in edit mode, swapped to secondary pane from main. The Skew-T 'parameters' and 'control' pop-up windows are still present on desk-top while IST/edit mode is not in the main pane. When IST/edit mode is swapped back to the main pane, the pop-ups are suppressed (when they should be present) requiring you to toggle IST table to retrieve them.

  Workaround: Toggle pop-up windows off and on.

• Problem: Interactive Skew-T (IST) - Editable Mode DR 1108
  When swapping IST/Editable from secondary to main pane, lost hodograph and Skew-T 'parameters' and 'controls' pop-up windows were still visible (after toggling IST table).

  Workaround: None

• Problem: Interactive Skew-T / editable mode - print capability DR 1116
  'Skew-T parameters' pop-up must have a 'print' capability. The data must be readily accessable when evaluating severe convective systems. Also make IST 'parameters' output available in the text browser.

  Workaround: None. This is an enhancement to the Skew-T.

• Problem: Error in Skew-T analysis DR 1117
  Skew-T (LCH 30nov97@12z) Analysis: LCL 674ft; IST; LCL 3322ft. Analysis: Initial Parcel Temp /Td67/38F; IST: Initial Parcel Temp/Td51/41F Probably an error in the Skew-T analysis, not in ISL, determining the initial parcel temp. (IST = Interactive Skew-T)

  Workaround: None

• Problem: Some Plotted RAOBs never report data DR 1435
  Using Upper Air:UA plots:RAOB:300mb RNK, UCC, GEG and some Canadian RAOB stations were plotted but did not report any data, for the week starting March 8.

  Workaround: None

Surface Problems

• Problem: KOJC and KOYZ not plotted correctly for EAX DR 1221
  KOJC is plotted too far West in Johnson City, Kansas. KOYZ is not being plotted on the map or text monitor.

  Workaround: None

• Problem: Ceiling value not plotted correctly on Ceil/Vis plot DR 1287
  The Ceil/Vis plot on D2D shows cloud cover and visibility information for metar stations across the country. The number in the upper left of an individual station plot is the ceiling height in 100's of feet, decoded from that stations's METAR observation. It was noticed in ICT on 3.1 when this ceiling is coded as VV001 (the VV is used when there is an indefinite ceiling or very low visibility, e.g. fog), instead of the normal OVC001 for example, the Ceil/Vis plot will incorrectly show an M for missing the ceiling on the plot, when it should show a 1 (one) in the above example. It appears that the system is not properly decoding the ceiling information when the VV designation is used in the METAR.

  Workaround: None

• Problem: Max/Min Plot from NCEP plotted incorrectly DR 1356
  The Max/Min plot (under Surface menu) has been plotting inconsistently. Sometimes only Canadian Data would be displayed, sometimes neither. Also there is a geographic registration problem with plotting temperatures over bodies of water.

  Workaround: None

• Problem: Put home cursor misidentifies most military METAR stations DR 1431
  PutHomeCursor is still misidentifying most military Metar sites, such as: 1) Listing a nearby town or city at the site instead of the actual military installation (e.g., KADW lists Morningside MD rather than Andrews AFB MD; KFBG lists Bonnie Doone NC instead of Ft Bragg NC; KSSC lists Oakland SC rather than Shaw AFB SC.

  Workaround: None

• Problem: Precip Plot Error DR 1305
  There are discrepancies in the values for 24-hr, 6-hr, 3-hr, and 1-hr precip plots and the Metars that are received over AFOS. For example, KLYH displayed .53 inches for the 6-hr plot 18Z 4-Feb-98 while the 18Z Metar report .90 inches for the 6-hr precip.

  Workaround: None. Check the Metars Text data.

• Problem: Error received in Metar Plots DR 1252
  TAR reported receiving bad Metar Plots (dew point reading higher than dry bulb temp).This seems to only occur when the statue mile (SM) entry is missing.

  Workaround: None

Grids Problems

• Problem: Density DR 1307
  In may cases, with several different grid products (Thickness, Lapse Rate, Vrt Temp Change, Rel Humidity, Height, Temp, Vorticity, etc.) the grid product will show a smaller density level when Max is selected. Of ten the density is less than 1, when Max is selected.

  Workaround: Do not select Max; select the highest number value.

• Problem: AVN Model soundings not working for Nhemis Scale DR 1295
  For the Nhemis scale, you can plot a model sounding from the Volume Browser by selecting AVN or MRF from the Scale menu and Sounding from the Other menu. Trying to plot the model soundings for the AVN model, all 10 soundings had bad plots. One out of ten MRF soundings had a bad plot.

  Workaround: Use North American or CONUS map scale.

• Problem: Problem when loading previous version of a MesoEta product DR 1009
  AWIPS currently saves only the latest version of the MesoEta model in the database. If you try to load the previous version of that model, nothing happens. The operator should at least receive a red banner message stating there is no inventory for that product. Also, if you try to load another product into that same pane, a time-match error alert is displayed to the user.

  Workaround: Clear the panel before loading another product into that panel.

• Problem: ETA Model Precipitation Error DR 1092
  The Eta Precipitation field differs from the current PCGRIDDS product in that AWIPS show a .01 contour where PCGRIDDS shows 0.

  Workaround: None

• Problem: 6hr/24hr MesoEta Precip DR 1328
  There are discrepancies between the 6hr and 24 hr precip plots ending at the same time.

  Workaround: None

• Problem: Some Grids are not being decoded DR 1223
  ngm202, ngm211
  RUC/regConus/GH/sfc(0,0)no level index for pane surface
  Eta48/regConus/GH/sfc(0,0) no level index for pane surface
  NGM/regConus/GH/sfc(0,0) no level index for pane surface
  ASSI/hemis/uW/LBIS930,0/no level index for plane Blyr
  ASSI/hemis/vW/LBIS(30,0)no level index for plane Blyr

  Workaround: None

• Problem: PuertoRico, Hawaii, and Alaska grids are not being decoded DR1225

  Workaround: Not used at this time.

Volume Browser Problems

• Problem: AVN Cross section not working at North American scale DR 1471
  Cross sections of AVN data on North American scale does not display.

  Workaround: Display the AVN cross section at another scale.

• Problem: Eta and MesoEta Lifted Index Time Series Plots DR 1480
  The Eta and MesoEta Lifted Index Time Series is plotting in negative kelvins.

  Workaround: None

• Problem: Geostrophic Wind Speeds from Product Maker and Volume Browser DR 1519 This DR is also in the Product Maker section.
  Geostrophic Wind Speeds from Product Maker and Volume Browser don't always match. Wind direction was always the same; however, wind speeds from Product Maker are generally larger than those form the Volume Browser at higher latitudes, and are generally smaller at lower latitude.

  Workaround: None

• Problem: Volume Browser settings problem DR 1280
  In the Volume Browser, the "Cross-section" setting does not revert back to the default setting of "Plan view" when the clear button is selected, like the "Animate in space" button reverts back to the default of "Animate in Time" upon clearing.

  Workaround: None

• Problem: Difference From Volume Browser DR 1290
  If you create a difference product form the Volume Browser, then display it in the Large Pane, you can not use the third mouse button over the product legend to display the product as an image. IF you loaded it as an image, you can not display it as a contour from the third mouse button over the product legend.

  Workaround: None

• Problem: Time Series Data Plots DR 1405
  When bringing up a Time Series with Surface Temperature(F) and Dew Point graphed, the NGM and AVN show separate data plots on the y-axis. This makes the graph confusing and hard to read because the dew-point line is crossing the temperature line.

  Workaround: None. Pay attention to y-axis labeling.

• Problem: Precip Accumulator Error. DR 599
  In the time series display window, instead of data points the display is a solid bar of red or yellow which continues from around March and April of 1996 until present time and even beyond. This does not occur for time series lengths of a few months but does occur for lengths of a year and greater.

  Workaround: None

• Problem: QPF fields in gridded data DR 658
  A difference was noted in the AVN model QPF fields when comparing WFOA displays with the N-AWIPS display. The discrepancy involved the 60-72 hour projections. Essentially, when displaying the 12Z run of the AVN model, the WFOA system indicated we would get close to 1/2" rain in the DCA area while the N-AWIPS indicated all rain would pass to the south.

  Workaround: None

• Problem: MSAS appears in the Volume Browser sources menu, even though MSAS will not be available until Build 4.1.

  Workaround: Don't use it.

Radar Mosaic Problems

• Problem: Radar Mosaics plot each radar separately rather than plotting them together. DR 635/688
  In some cases radar mosaics plot each radar separately rather then plotting them together. If data for one radar out of the many was missing, AWIPS automatically assumes that the inventories are unsuitable for compositing and gives a separate inventory time for each product.

  Workaround: None

• Problem: Time Matching - Radar Raster Products DR 1437
  Using the Mosaic Menu, selecting composite products, returns incomplete criteria , producing unreliable results.

  Workaround: None.

Radar Products Problems

• Problem: VR-Shear Tools function not working DR 1460
  The VR-Shear tools function does not work when displayed with a velocity radar product. The tool is editable but no data is displayed.

  Workaround: Make sure that both ends of the segment are on actual data pixels, not over data-void areas.

• Problem: You can't individually magnify the VR shear overlay (from the pop-up menu).

  Workaround: Do a global magnification from the menu.

• Problem: Range Rings - 1km Composite Ref (CZ) DR 767
  Range rings cannot be displayed on 1km Composite Ref (CZ)

  Workaround: None

• Problem: Changing magnification has incorrect effect on Storm Track Info text DR 787
  Increasing the Magnification on displayed Storm Track Info data displays the storm information smaller and compressed to the left side of the display. Decreasing the magnification displays the information larger and more spread out to the right side of the screen.

  Workaround: None

• Problem: CFC can't be displayed
  Though the CFC (product #34) is now available through the one-time request, there's no way to display it.

  Workaround: None

• Problem: WER product: user needs to be able to select elevation cut
  WER (WkEchoRegion) product: user needs to be able to select the elevation cut (bitmap)

  Workaround: None

• Problem: Distortion on storm total precipitation radar graphic DR 1383
  Kansas City reported distortion on radar graphic displaying the storm total precipitation. There was a blackout line at the 360 deg angle.

  Workaround: None

• Problem: Raster Radar products are not compositing properly DR 1242
  In some cases when Radar Raster products are displayed, there will be a pixel distortion.

  Workaround: None

• Problem: Derived Radar Graphic - Storm Track Info with numerous storms DR 770
  The Storm Track Info product is being displayed with the text panels overlaying the image; thereby preventing the analyst from viewing the image. Zooming and/or roaming did not correct the problem. An image with fewer storms displays correctly.

  Workaround: This is fixed in Build 4.0 with a multi-load of several overlays, each including one row of storm information.

Satellite Problems

• Problem: Active Cursor Error in WV/IR Satellite Image DR 1293
  Active Cursor will display incorrect data on the WV/IR Satellite image. At temperatures above -35 degrees, they are displayed as < -35 when it should read > -35 degrees.

  Workaround: None

This page is maintained by Fran Curnow.

Last modified: 8 May 98