[Ncep.list.idp.mrms.users] OPEN - TID: 809080283 - IDP - URGENT: Paducah radar data not being used in MRMS (since at least12z)?

Mark Fenbers - NOAA Federal mark.fenbers at noaa.gov
Sun Sep 9 11:46:45 UTC 2018

But even with the PAH down for maintenance UFN, this shouldn't leave a hole
in the product.  Radars go down throughout the country fairly often, and
when this happens, MRMS data is filled in from surrounding radars.  But
with the PAH outage, this fill-in from other radars is not happening like
it usually does, and THIS is where the problem exists -- where the MRMS
product is created.   I hope this clarifies things.


On Sun, Sep 9, 2018 at 7:40 AM NCO <toc.nwstg at noaa.gov> wrote:

> Ticket Properties
> Ticket Number: 809080283
> Opened: 2018-09-08 19:54:10
> Status: OPEN
> Category: IDP
> Description: URGENT:   Paducah radar data not being used in MRMS (since at
> least12z)?
> 2018-09-09 11:37:31 GMT [NCO-MCL] NCO called the Lead Forecaster at PAH
> and he reported that the issue is with the Radar itself. Since there is
> weather in the area, technician would like to wait until weather cleared
> before working on the radar further.
> ===================
> 2018-09-09 11:32:06 GMT At 1120z, On-Call IDP Sys Eng, Vanessa called with
> update that she is researching to see what options may exist, if any, at
> the systems level, to enhance MRMS output. At this time, it remains
> uncertain. Vanessa is also going to consult with Senior IDP Eng for
> additional input. //JOHN//
> ===================
> 2018-09-09 11:01:42 GMT At 1050z, NCO-Tech Control consulted with SDM, and
> then called IDP oOn-Call System Eng, Vanessa M. Informed Vanessa this
> ticket has been upgraded to URGENT, based on input from Sr Meteorologist
> from Wilmington OH, RFC, and we are interested in determining what type of
> action, if any, can be performed on MRMS system, to allow whole to be
> filled by surrounding Radar's, short of Radar repair outside of RADAR
> repair, at KPAH. Vanessa will take a look to determine what actions can be
> performed and will report back. //JOHN//
> ===================
> 2018-09-09 10:44:08 GMT At 1028z, received e-mail update from RFC Senior
> Meteorologist, Mark, F:
> Well, I don't know who Scott talked to, but it IS critical to OHRFC!!
> We've got the biggest event we've had in a very long time and this is
> affecting one of our most important products that multiple agencies depend
> on. How can this not be considered critical??! //JOHN//
> ===================
> 2018-09-08 20:54:42 GMT 2021Z - Received email notification from the SDM:
> NCF called and also reported the same to the SDM. There are no MRMS issues
> in BB. Sent an E-mail to IDP on boarding support. 2007Z - Talked to Scott
> at NCF and he reported that after receiving feedback from several RFC sites
> it was deemed non-critical and could wait until Monday.
> (SEC)
> ===================
> 2018-09-08 20:02:46 GMT 1857Z - Received email notification from Ray
> Davis: i there,
> I bet that someone has already reported this, but just in case... The KPAH
> dual-pole radar products seem to be missing, and MRMS seems to be
> preventing the surrounding radars to fill in the void. The problem appears
> to have started sometime after 12z this morning. Could you check into this?
> The KPAH hole didn't appear after we processed our grids up through 12z,
> but it appears that MRMS is now backfilling previously saved grids with bad
> data. The Following FTM was issued from the WFO in reference to this site:
> KPAH 062106 FTMPAH Message Date: Sep 06 2018 21:10:57 THE KPAH RADAR IS
> (SEC)
> ===================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.lstsrv.ncep.noaa.gov/pipermail/ncep.list.idp.mrms.users/attachments/20180909/6e9d0927/attachment-0001.html 

More information about the Ncep.list.idp.mrms.users mailing list