FYI: The image above shows my LightningCast forecast setup on my AWIPS workstation at NWS Pueblo. All Ltg data plots in the upper left, and the lightningcast is in the upper right. I prefer lightningcast as an image (vs contours), as the image shows ALL of the probabilities.
Today we are tasked with both IDSS and Warnings for the Austin TX area. I have been doing warnings while my colleague Nick has been doing DSS (2 sites). Once again Lena picked two excellent sites as the strongest of the day went right over the 2 DSS sites. As the storm approached the first DSS site, it intensified, and I decided to issue a warning based on subtle cloud top cooling, the gradient with the storm and the MRMS trends in hail size. At the time I issued the warning a 1 inch hail report came in.
Late yesterday, Kevin was able to put Stoplight in the AWIPS instances. During luchbreak today, I was able to create a procedure which married the ltg stoplight product with LightngCast. We used this today for our DSS. As mentioned earlier, Nick was taking care of the IDSS so I did not look at the ltg data as much as I wanted to. Below is a loop of the data and the storm we were warning for….
Image above…the married “ltg cast” and “ltg stoplight” (upper left panel).The marginal severe storm (vcnty Austin) is in the lower right image. I really like the fact that we can marry the two lightning products into one (unfortunately, this can only be done cleanly with AWIPS, although it may be doable within the GR environment (but would be really cluttered))
Just some thoughts…A lot of the ltg data above is based primarily off of the GLM. The GLM has an exaggerated footprint of 8 x 8 km. Hopefully, with the new ltg mapper which will eventually come on line in several years will have a smaller footprint. Based on the way things are now, We are likely “overwarning” for the lightning threat when we do DSS based off of ltg stoplight and LightningCast.
Some more thoughts, with the HWT ending tomorrow, the most obvious product that needs to be put into operations in the SZA sat pix products. THE SZA has the biggest bang for the buck and should be easily do-able (but I am no AWIPS software expert). The lightning products (Ltgcast and Stoplight) are also very valuable tools, but need to be simplified as these tools are not ready for public consumption (even though they are public facing). The OCTANE products are impressive, but need alot of work before they are placed into AWIPS (The OCTANE site on the CIRA website is the place to go to see this data the best.
Here are some suggestions on making things a bit easier for the forecasters for the next HWT:
Have IDSS parameters defined ahead of time, i.e., ‘For IDSS point A, wind criteria is 40 mph, any lightning, any hail. Let us know if any of these parameters get within 10 miles of my IDSS Site. Once the weather threat is 10 miles outside my circle, let me know”. In a nutshell, pretend you are the emergency manager for that site.
Set up AWIPS so it defaults with the maps of the CWAs, cities, county names already plotted. Make sure the density and magnifications are appropriate.
A 4 panel radar display of R/SRM would help. Set this up for all radars that will be used on this day. See below for a good display setup
I think it would be better if the teams were either doing IDSS or Warnings, but not both at once. That way we can work together and learn (bounce ideas off each other in realtime). If one is doing IDSS and the other is doing warnings we really can’t share knowledge amongst ourselves (we are too focused on our separate responsibilities).
Some last second things….we noticed that ltg cast was having issues of not detecting lightning in Colorado….
-Mesovortex