Large ProbSevere Blob

Here is one drawback of ProbSevere that has been briefly discussed. The areal extent of the identification is not based off of some of the features that feed into it, but rather the dBZ reflectivity representation. In this case, for a MCV and line of storms, the blob below is approximately 152 miles long using a center line to calculate the distance. ProbSevere kept this size of storm for two 2 minute calculations before breaking the storms apart into several different identifications.

-Alexander T.

THE 3 MARCH 2019 CASE FOR AZSHEAR – #5

Now here is an example of where the single radar AzShear product would have provided me with some lead time with respect to grabbing my attention sooner in further interrogating a tightening circulation embedded within the heart of the QLCS. As for the merged products, I was unable to gain any insight with those products for what appears to be this relatively shallow circulation.

~Gritty

Merged 3-6 AzShear picking up on mesocyclones early

A

In watching for convection knowing that later in the simulation there will be tornadoes produced in the FL Panhandle, I took a peak at each product prior to convection. Single radar AzShear is a little far away and doesn’t pick up on it but the merged products give an early indication that a supercell is developing and beginning to rotate. Knowing this storm will produce a tornado this is very helpful as a heads up.

 

— lakeeffect

THE 3 MARCH 2019 CASE FOR AZSHEAR – #2

Looking at the 0-2km merged AzShear product, my attention was drawn to the line stretching to the SW of the KMXX radar. While I see utility in using this product more for SA, the SAILS artifact of not having the images lined up properly could lead to false interrogations of what’s actually occurring. In this first image (below), the wind field is apparent. In the second image, it looks like the wind field has separated. In the last image, it’s very clear that a slice being merged into the product shows the wind field significantly separated.

~Gritty

The 3 March 2019 Case for AzShear

The single radar AzShear product made a rapidly developing tornado very apparent, forcing my attention to be pulled to it (first image, below). Additionally, it was very interesting to see the RFD so clearly (second image, below). However, as noted previously, I do have some reservations about the number of false alarms that it may be picking up, as seen in the last image (below). But, there is a lot of promise for this product to serve as an enhanced SA tool and/or increase confidence in the warning decision-making process.

~Gritty

Single Radar AzShear 3/03 Case

A

Seconds into this simulation it’s apparent that an embedded supercell is about to wreak havoc. It’s incredible how well you can examine the anatomy of the thunderstorm using the Single Radar AzShear product. It’s still apparent in the merged products that there’s an area of concern, but you can’t quiet examine the anatomy of the thunderstorm like you can in single radar.

B

In B, the merged 0-2km  it’s clear where we should be paying attention, but trying to diagnose the structure of or the maturity of the thunderstorm is much more difficult.

 

-lakeeffect

Spike in Merged AzShear Product – Wed Apr 24

Noted a big jump in the merged 0-2km AZshear product – see below.  This caused a corresponding jump in ProbTor.  Also note the “double peak” likely caused by SAILS scans.  This is an a favorable location with > 30kts of 0-3km shear – so mesovortex formation is possible.  Will be interesting to see if anything develops….