<div dir="ltr"><div>To all,</div><div><br></div><div>A summary of what IDP Onboarding has provided concerning this urgent ticket.</div><div><br></div><div><div dir="ltr">This is a recap of this morning's phone conversations. Initially
we thought this was an MRMS ingest issue so we restarted processing on
KPAH radar (vm-lnx-mrms-sr17a). This is before we got the email saying
it is a hardware failure at the site. Since some of the data is
coming in for the KPAH radar, MRMS does not know it has to fill in from
the other radars. In order for them to fill in we need to remove KPAH from
MRMS completely. This requires a config file change and a restart of
MRMS processing on that VM. The problem with this is that it
would cause WFO Paducah to lose the local radars products for KPAH which are
still coming in. Based on this I understand you do not want us to make
the change and we will stand down.</div><div dir="ltr"><br></div>Randy<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 9 September 2018 at 11:53, NCO <span dir="ltr"><<a href="mailto:toc.nwstg@noaa.gov" target="_blank">toc.nwstg@noaa.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ticket Properties<br>
Ticket Number: 809080283<br>
Opened: 2018-09-08 19:54:10<br>
Status: OPEN<br>
Category: IDP<br>
<br>
Description: URGENT: Paducah radar data not being used in MRMS (since at least12z)? <br>
<br>
2018-09-09 11:52:28 GMT At 1146z, Mark F, e-mailed further clarification:<br>
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. //JOHN// <br>
<br>
<br>
===================<br>
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. <br>
<br>
<br>
===================<br>
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// <br>
<br>
<br>
===================<br>
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// <br>
<br>
<br>
===================<br>
2018-09-09 10:44:08 GMT At 1028z, received e-mail update from RFC Senior Meteorologist, Mark, F:<br>
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// <br>
<br>
<br>
===================<br>
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.<br>
(SEC) <br>
<br>
<br>
===================<br>
2018-09-08 20:02:46 GMT 1857Z - Received email notification from Ray Davis: i there,<br>
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?<br>
<br>
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 OPERATIONAL WITH DEGRADED DUAL POL PRODUCTS. DUAL POL PRODUCTS SHOULD BE USED WITH CAUTION. REPAIRS WILL BE MADE TO THE RADAR EARLY NEXT WEEK.<br>
<br>
(SEC) <br>
<br>
<br>
===================<br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Senior Duty Meteorologist<br>NOAA/NWS/NCEP/NCO/OMB<br></div></div></div>
</div>