DSS in the Birmingham CWA

 PHS

The initial outlook on the PHS model shows limited potential in the CAPE and STP in this area around the DSS at 20Z. However, it shows an increased potential for 21-22Z which may be the time of most concern for my DSS area.
The initial 20Z model showing limited instability and the contoured ProbSevere to show ongoing convection.
PHS shows a tongue of instability and associated STP as the main convective line lifts northward. This would indicate that the main concern would occur around 22Z.
Based on the line of storms to the west of our DSS event and the associated shower activity lifting northward ahead of the line, the PHS model was accurately representing the convective potential. LightningCast also shows a decrease during this time period which increases consistency and confidence in what the forecaster is seeing.
“Verification”
 
This lack of convection was observed as showers moved through the area without any lightning or wind potential. There was some redevelopment behind the line and to the south of our event that indicated some concern. At 22Z, you can see the line of storms already being analyzed by ProbSevere lining up nicely with modeled instability and other plotted severe weather parameters.
ProbSevere contours and PHS model line up nicely in the 22Z 2-hour model forecast and show consistency in where the area of greatest concern is likely to be.

LightningCast & GLM for DSS

Initially the LightningCast for our DSS event surged to near 50% or slightly above. This was an initial concern for the DSS area.
As these storms weakened, the probabilities of lightning also fell to under 25%. I liked that these probability decreases were not rapid, but a gradual fall after the initial peak. GLM and LightningCast both had a consistent drop in probability and lightning activity as the “storms” weakened.
It is becoming clear that the rate of change of all of these satellite products is the most important information that a forecaster can gain. While an initial picture of the probabilities looks concerning, pairing this with other satellite products for context and seeing the overall trend of this data led to an easy decision to wait for additional data. Taking this at face value would lead to a quick (and potentially unnecessary) reaction.
Initial threat of lightning as illustrated by the LightningCast product.
The showers on the SE side of this line have decreased in intensity and have lost most of their lightning potential. The probabilities have decreased accordingly.
LightningCast, GLM, radar, and satellite showing the decreasing trend in lightning threat and the approach of moderate to light showers on the DSS event.
Showers are expected within the next 30-40 minutes and the trend in lightning appears to be going down consistently. GLM has also been helpful in showing that no cloud flashes have been observed at this stage.
There were some minor inconsistencies that I noticed since the Meso-sectors were both over our CWA. These were mostly minor, but I noticed at one point, a location had a probability of >50% or 0% and did not intersect with GLM measurements.
Inconsistencies in GLM and LightingCast Meso1/Meso2 probabilities. It seems the accurate probability here was 0% based on the lack of ground-based lightning network reporting.
As PHS indicated there was a second and more concerning wave of convection moving from the SW toward the DSS event area later in the afternoon. GLM and LightningCast probabilities both show the strengthening of this pulse and the increased lightning activity as it moved into the BMX CWA.
21:26Z, the storm indicated a 10% chance of lightning at the DSS event area.
21:36Z, the storm indicated a 50% chance of lightning at the DSS event area.
The 45-minute warning was given at 21:50Z to the event coordinator that a storm with the potential of producing lightning and winds in excess of 30 mph was approaching the event area. GLM was a key part in this decision as it continued to show strengthening with lightning pulses indicating that the storm was at least maintaining its strength. The LightningCast probabilities were also increasing as they approached the area with the 75% contour moving into the area by 21:52Z.
GLM (top) and LightningCast at the 45-minute DSS decision point.
The pulses weakened significantly as it approached the area and this was consistently evident in the GLM display and the LightningCast probabilities.
GLM (top) shows the MFA increasing and the FED decreasing. This was consistent with radar data and observed lightning pulses. The LightningCast probabilities also decreased.
Lightning occurred in the area around 22:38Z with GLM showing another pulse beginning as the storm moved through our DSS area.
In general, I found GLM to be much more useful today outside of the supercellular mode with more multicellular convection observed over central and southern AL and especially so for identifying strong cells within a linear structure.

ProbSevere v3

In a DSS setting there isn’t a real reason to use ProbSevere v3 because winds far below the 50-knot threshold could cause problems at our DSS events. That being said, there was great information in the trend graphic as I could see the growth and decay of storms that were already in progress. This allowed me to focus my attention on the strongest storms.

NUCAPS

Ongoing convection ahead of the line of storms limited the NUCAPS ability to produce good data. Availability of soundings was also an issue as the data came in between 19-20Z with storms ongoing near my area of interest.

Optical Flow Winds

For the optical flow winds, there wasn’t much in the way of DSS that I could find a use for. The divergence field again could be useful, but with the suite of GLM I was seeing the divergence and strengthening of the storms in multiple products. Visualization is still the main hurdle with OFW.
Once the anvil for some of these storms developed it was difficult to use. Especially as debris clouds developed and overspread the area in advance of additional convection behind the initial line.
– Overcast Ambiance

Analyzing the convective environment prior/during storm activity

I decided to look at the various parameters prior to storm initiation. When looking at PHS, it appeared our prime time for storm activity was going to be 21-00Z, when SBCAPE was forecast to be high, along with low LIs. I noticed that the STP was also elevated, upward of 3 as the activity moved northward into the southern portion of our CWA.

When comparing this to the SPC mesoanalysis page, the parameters from PHS seemed to agree fairly well with the mesoanalysis. It did appear, though, that the STP was a tad faster than what the mesoanalysis page showed. And the PHS decreased the instability an hour or two prior to 00Z, whereas the SPC page showed that instability remained elevated up to 00Z. The STP parameters in the PHS were a tad higher than the mesoanalysis page as well, with the meso page only 0.5 to 1.

A look at the NUCAPS soundings in SharpPy showed a relatively stable surface layer in observations at 12 UTC. By 1550 UTC, NUCAPS showed the surface layer to heat up from insolation but still remain largely stable.

Looking at NUCAPS gridded data, specifically for mid-level lapse rates, while the gridded data was noisy with some bullseyes, it did show the environment between 3 to 5 degC/km lapse rates, consistent with the SPC mesoanalysis page (which showed around 5.5 degC/km).

Just prior to more storm activity, GLM was picking up on a cell moving north into Wabash County, where a spike in MFA and decrease in TOE was evident. This storm was eventually warned on, where the radar showed a TBSS with a ProbSevere threshold for wind near 28%.

The lightningCast model, at least for KIWX, appeared to do better today in terms of the advection component, with the lightningCast downstream of the cells depicted in MRMS.

This time period was at 21:44Z, showing again how lightningCast was showing better predictive capabilities downstream of current convection.

Snowfan

Monitoring Scattered Convection in northern IN & Tin Caps DSS

I decided to submit a quick DSS briefing for the Fort Wayne Tin Caps with DCPD indicating glaciation and weak echoes on radar. LightningCast was starting to increase over northern IN for that weak developing convection. Additional convection is spreading in from the south, and higher LightningCast contours are also spreading in. PHS shows increased CAPE over the next hour.

Left: DCPD with GLM and LC. Right: Base reflectivity with LC

Loop of base reflectivity and LC from 1938 to 2014Z:

Left: PHS forecast CAPE at 20Z. Right: PHS LI at 20Z

First GOES flashes a little after 20Z. DCPD with GLM FED and LC

However, by 21Z, lightning is limited pretty much to cells to the northwest and E/NE of Fort Wayne.

Happily, LightningCast called the lightning flash east of Fort Wayne about 10 minutes out (small pink circle east of Fort Wayne)

Why is barely anything happening? Convection looks to be “firing” now on an instability gradient. Indicated by PHS at 21Z:

Am I confident that things will ramp up at all for our area within the next couple of hours? So-so. Here is PHS CAPE and LI for 21Z.

And gridded NUCAPS 850-500mb lapse rates at 1730Z, ranging from around 4.5-6C/km

However, zooming out, there is an area of convection across central IN that should begin approaching our southern CWA boundary within the next half hour. Here is the GLM 4 panel with GOES clean IR underlaid with the FED, at 2130Z.

– PoppyTheSmooch

Memphis, TN Synopsis

Synopsis

An upper low and cold front is expected to move across the lower MS Valley. As the upper low moves east today, weak shortwaves embedded in southwest flow will lead to a marginal risk of thunderstorms as they form along and ahead of the front over the Memphis region. The main concern was a moderate risk of excessive rainfall for this afternoon/evening.

IR imagery. Upper low located near the OK Panhandle.

Surface analysis map of the surface low and attendant front.

Surface observations as of 4:00PM CDT.

SPC Day 1 Convective placing TN at a marginal risk.

MLCAPE ~500 J/kg.

PHS displaying weak CAPE/LI values and a well-defined dry line just west of AR.

WFO Memphis headlining excessive rainfall outlook.

WFO Memphis headlining marginal risk of severe storms.

Most of the severe storms were east and south of our area of interest shown here with GLM.

GLM overlaid with Radar.

GLM overlaid with satellite imagery.

LightningCast

ProbSevere3 showing a low risk of thunderstorms.

Optical Flow winds show an area of divergence over eastern and southern AR/TN border.

Vortex Power

BMX – Daily Updates

GLM proved useful early on in combination with MRMS VII. It showed areas of strengthening storms that were reflected in radar later. A pair of severe warnings were then issued.

This was a good prob severe null case where odds remained steady along with stationary or declining GLM values. A correct no-issuance followed even with base velocity showing 50 kts or so of wind on the lowest scan. Some other prob severe oddities occurred during the day such as odd object tracking and weird percentage changes. QLCS tornado odds seemed too low as discussed. Overall though, it continues to provide useful information.

The PHS forecast again correctly identified the highest risk areas where storms strengthened and tracked. It mirrored other sources so I would still like to see if overall it is better or not.

Prob severe highlighted this storm ahead of time before it went severe in Mobile’s area.

NUCAPS provided limited use today. Overall, heavy cloud cover limited usefulness of a number of products compared to the clearer case in Texas the day before.

Some Random Guy

MAF Testbed Observations

ProbSevere v3

For the initiation of convective storms, I found that the ProbSevere performed the best over the other products available to me today. I have seen over the last couple of days that the best use of ProbSevere is the trend table. The steep increase in these total severe values support radar trends that suggest a warning is necessary. For the initial warning on severe storms, this was the best use.

The only negative to this product was the latency. While the latency was only on the order of 2-5 minutes, this was equivalent to appx. 2 radar scans that indicated to me ahead of time that this storm was strengthening. This can lead to some confusion especially if the storm is quickly pulsing and falling.

Additional upticks were noticed in subsequent SVR issuances throughout the afternoon that provided a nice heads-up in conjunction with the radar data. These were used in the context of the storm maintaining its strength after the storm was warned and again after the storm re-pulsed several minutes later.

It is also worth mentioning that the perceived threat of ProbSevere was also the shared opinion of the forecast (forecaster perceived threat for hail had the highest ProbS. probability). Once the storms reach the “cap” of their ProbSevere, it becomes of little use.

GLM

GLM was useful during convective initiation, but did best for storms that were already at the peak of the ProbSevere threshold. GLM showed additional pulses in a mature storm that had a 90% probability of being severe and added confidence to the warning forecaster that the storm had gained additional strength which manifested itself in larger hail for example.
It was however short-lived as the storm gained additional intensity but did not show the corresponding increase in GLM FED that one would expect. This was explained as a limitation due to the structure of a mature (and severe) thunderstorm.
Min Flash Area also reached its lower values on several storms which provided little to no additional data. Maybe this used in conjunction with total optical energy would be useful, but this yielded no significant results when investigating briefly.

PHS Model

The PHS model was very useful today ahead of convective initiation, but more so in an advective situation.
Instability parameters were observed as ongoing severe storms moved SW toward the established instability gradient. ProbSevere outlined areas are moving SW in the image below across an area of relatively high CAPE and low LIs. This provided useful information about the existence of a boundary and the motion of the storms along with the pre-conditioned environment.
The model did have limitations as the storms became ingested into the later runs of the model and the storms showed developed cold pools. The environment depicted in this situation had become dominated by nearby cold pools of incorrectly placed convection which limited the model’s usefulness.

LightningCast

Not much use of the lightning cast today due to the lack of CI within our CWA, but we did get a chance to look at the advection of lightning. In general, this proved to be a little too slow. It seemed the contours were tight to the storm and storm motion was rather slow, but the lead time on lightning detection was around 30-40 minutes. With an advecting storm, I would have expected this to be rather accurate to the 60 minute threshold that it attempts to achieve, but 30-40 minutes is still VERY useful for DSS and now-casting purposes.

NUCAPS

NUCAPS had some interesting results today, primarily in the way it reported green, yellow, and red data points. Some of the gridded data was unavailable for points with green-retrieval and this was puzzling because it would have indicated a dry slot over the DFW region that was evident in the water vapor and visible satellite. However, the data grid boxes were missing or contaminated with bad data over a mostly clear area. Areas with similar cloud coverage performed as expected. The pop-up skew-t continues to be the best tool in this suite of products, provided the data points are green-retrieval.

Optical Flow Winds

Not much use on the optical flow winds today due to the fact that ongoing convection muddied the data. Overshooting tops were visible for a brief moment, but quickly engulfed in strong storms and expanding anvils. The divergence field is really hard to gather meaningful intel from and the existing platform outside of AWIPS limits its overall usage. A suggestion in our group today was that divergence could be useful if the noise is limited. Perhaps remove values above and below a certain threshold. Instead of widespread values, draw attention to the important outliers.
– Overcast Ambience

Today’s details of products and warnings: Midland, TX

I found the PHS products useful for seeing the corridors of enhanced severe risk. They correctly showed that hail (or wind) was the highest risk compared to tornadoes.

ProbSevere was very useful with the trend lines. Again and again correctly identified risks as they occurred.

GLM showed strong ramp ups in activity prior to each severe issuance. No complaints here.

NUCAPS data was less useful, but with the skew-t pop up I was able to correctly see areas of mid level dry air. I did not use optical flow. Prob lightning was useful to see the first cells pop up but did not serve as much purpose after that with no known DSS opportunities.

Some Random Guy

ProbSevere on some early storms near ARX

We noticed a relatively high ProbSeverev3 (53%) on a rather innocuous looking storm (MESH around 0.5”) around 2030z. This was higher than the v2 value of 36%. The individual probs were relatively evenly weighted at lower values near 30%.

(clockwise from top left) MRMS 18dbz echo top, MESH, reflectivity and ProbSevere (storm in center), and low-level MRMS azimuthal shear.
(clockwise from top left) GLM FED, GLM MFA, reflectivity and ProbSevere (storm in center-right), and GLM TOE.

GLM FED was unimpressive, though it’s unclear how much of this is related to lower detection efficiencies in this area. ENI total lightning was halfway decent. High DCAPE values and other environmental parameters may have been sending the ProbSevere v3 higher.

Timeseries for the storm of interest.

Another storm further to the west over SE MN had slightly lower MESH (.39”) but in this case PSv2 was higher at 48% vs Psv3 at 23%.

– Barry Allen

Tags: None

Progressive Disclosure & GLM Flash Points

When loading GLM Flash Points, there is no preset density of the data.

This does affect how much flash point data is displayed depending on the zoom level of the map. In the 2 maps below, within the red square of the larger map, 13 flash points are indicated as opposed to 15 once you have zoomed in further:

Unless the forecaster knew to increase density to max, this could obscure some important clusters of lightning coincident with storm evolution.

– Guillermo

Tags: None

GLM Flash Points

Noted GLM flash points really help speed up the process of identifying where the cell of interest was located.  In the past, I would have to make a manual, on the fly “calculation” in my head where the actual cell was located.  If there was only one cell, that was easy by looking at radar.  When you get into the complex thunderstorm situations, that can be difficult and in the worse cases, it is too involved.  Seeing how the flash points seems to fix and/or surround the updraft, really helps speed this process up and give confidence to the forecaster which cell is the cell to be worried about.  This could also help with warning confidence.  The  image below shows an prominent example of this.

It is hard to see the flash points but there are 6 points surrounding the core of this small storm.  I chose this one to verify the positioning as it was on its own so it was easy to figure out which one it came from.  As such, seeing how close this is to the core, it makes it much easier to identify which FED “spike” is from which core.  

When looking at satellites with flash points, it also help confirm the location of the core as the ABI imagery is parallax corrected.

– Strato-Dragon

Tags: None