![]() | ||||||
| ||||||
Remote Backup Capabilities Are Now Available For RFC’sBy Jeff McMurphyPreviously, the plan for an RFC backup system was for the NWS Office of Hydrology (OH) to have the capability to load each individual RFC’s AWIPS system with the specific programs, tools, and data onto the OH AWIPS system. When backup operations were needed, an RFC would contact OH to initiate the loading of that RFC’s system and begin the data acquisition processes. RFC forecasters would then travel to OH in the Washington D.C. area, where they would use OH’s system to generate and transmit forecasts and products. In theory this seemed like a good idea, yet the logistics of maintaining accurate systems for each of the 13 RFC’s was too complicated. Another problem was the associated expenses of lodging and travel costs for the RFC personnel. Hence, this functionality could only be used in situations when the cost could be justified, typically not for the one to two day events which were most common. Thus, in these situations, the NWS WFO’s were on their own to issue river forecasts without the guidance of a hydrologic model. Recently, desktop PC processing power, storage capabilities, and software availability began to reach a level in which developing a backup system for local use at an RFC became a true possibility. In 2001, ABRFC began developing a backup Linux desktop PC. Linux was chosen because OH and the Forecast System Laboratory (FSL) had already begun the process of porting NWS applications to Linux. In May of 2002, this local desktop system was tested and proven successful for being able to provide ABRFC forecast and guidance products to customers in a timely and transparent manner. (Please refer to “ABRFC Operational Backup Test Is Successful” article in the Fall 2002 publication of “The Gage,“ for more details.) Since this first test, ABRFC has taken the backup capability to yet another plateau, this time in the laptop PC arena. The ABRFC has created a Linux laptop with the same functionality, yet with much faster processing speeds, nearly 7 times faster, than the current Operational AWIPS system. This system downloads data from the Internet, runs the hydrologic model as well as supporting programs such as NMAP, XNAV, XDAT, FCSTPROG XSETS, P2 and MPE and issues a full suite of operationally critical products and forecasts including RVFs, FFGs, HMDs, and HCMs. The AWIPS D2D Display is not utilized, yet radar reflectivity and satellite images can be displayed via a variety of web sites. The national Flood Outlook Product cannot be produced as ArcView is unavailable for Linux. Product dissemination is accomplished by using ABRFC developed scripts which drop products on a SRH server where they are picked up by a backup office’s LDAD. Products are then moved through the protective firewall from LDAD and into AWIPS via common LDAD/AWIPS ingest software. The advantage of the laptop portability was utilized during the test conducted on March 11, 2003. The test mimicked a total office-loss scenario and operations were conducted from a hotel room with a high speed internet connection as well as a second voice line for coordination purposes. The system was cold-started and made ready for use in one hour and ten minutes. Cold-start is defined as the system having no model files, no observed data, no files of estimated radar precipitation, no Quantitative Precipitation Forecasts (QPF) files, and not connected to the Internet. Ready-for-Use is defined as: the hydrologic model run, for the entire river forecast system, is complete along with a current set of data and the system is functional and ready for interactive use by forecasters with data ingest and dissemination processes up and running. This cold start is possible because on a regular basis, ABRFC’s operational hydrologic model information as well as other data is uploaded from a desktop version of the Linux backup system which we locally maintain. (Note: A data conversion problem exists for sending files from HP UNIX to Linux. Hence, once we transition to performing routine operations on a Linux platform, we will then be able to use this data rather than maintaining the desktop backup system.) Not only did this laptop PC perform all operational functionality, but it was also able to perform as a “server” in the sense of allowing multiple laptops to remotely login and allowing these “clients” to be used as additional stations from which to forecast. With the success of this latest test, SRH has provided the funding for the other Southern Region RFC’s, West Gulf River Forecast Center (WGRFC), Southeast River Forecast Center (SERFC), and Lower Mississippi River Forecast Center (LMRFC), to have a laptop Backup PC. Hence, by the time you receive this newsletter, ABRFC will have configured these RFC laptop PC’s for the specialized operations of each RFC and will have trained a member of each of the RFC’s in its use. Final testing and implementation of these backup systems is expected to be accomplished by July 31, 2003. So, in the near future, all Southern Region RFC’s will be able to provide services and products to the WFO’s and public in the events of an AWIPS upgrade, an AWIPS failure, or even in the case of a catastrophic event happening at an RFC’s building facilities. Back to top | ||||||
ABRFC Evaluates New Short-Term Probabilistic ForecastsBy Bill Lawrence | ||||||
Figure 1: Example of the Experimental Probabilities Plot of Flow through five days for Carthage, MO. This plot was generated with three inches of QPF forecast to occur in the Second Period, between forecast hour 6 and 12. The plot in purple shows the most likely flow/river stage situation while the plot in aqua indicates the least likely flow/river stage solution. | ||||||
| Back to top | ||||||
2003 Water Supply SeasonBy John SchmidtThis year, a dry winter gave way to a normal spring snowpack in the Arkansas River basin by the middle of March (See Figure 1). This catch-up was thanks to a record-setting blizzard on March 17-19, 2003. Although the bulk of the snow fell north of the Palmer Divide, the one to four feet that fell in the mountains west of Colorado Springs and Pueblo was welcome moisture. With most of the snow falling east of Salida, CO, snowmelt forecasts on the Arkansas River at Granite and Salida, CO remained about the same. However, snowmelt forecasts for the tributaries of the Arkansas River east of Salida (Grape and Chalk Creeks and Cucharas, Purgatoire and Huerfano Rivers) jumped from 71 to 94 percent-of-average snowmelt volume. Basin-wide, a slightly below-normal snowmelt season was forecast with a peak flow during the first two weeks of June. This forecast remained about the same from April to May. The timing of the snowmelt is based on an average distribution of runoff over the past 20-50 years and therefore reflects an average daily temperature. The amount of streamflow forecast through the summer reflects a normal amount rainfall, as most of the snowpack is gone. May proved to be anything but average, especially the last two weeks, as temperatures in the Arkansas River Basin ranked "much above normal" (See Figure 2). Additionally, areas above water supply forecast points received below-normal precipitation amounts over the past 90 days (See Figure 3). This significantly atypical temperature distribution resulted in higher and earlier than expected crest of streamflows at most water supply forecast points in the Arkansas River basin (See Figure 4). In fact, several flood forecasts and river flood warnings were issued for the Arkansas River near Canon City and Pueblo by the ABRFC and the local NWS forecast office in Pueblo, CO during the week of May 27th.
| ||||||
Arconyms in this Edition
| ||||||