Merged products end up showing trend information as new sails cuts come in. In the cases below, notice that the northern storm’s AzShear is weakening over time and the southern storm is increasing.

Above, you can see on the northern storm that the last tile shows weaker leading AzShear. At the same time, note that the leading AzShear signature in the southern storm is increasing.

The northern storm continues to dissipate as the upper tilts catch up to the sails cuts that were weakening earlier. While the southern storm continues to increase in AzShear intensity as the sails cuts would suggest.

At this point the northern storm is gone and the southern storm is quite strong and large.

So not only does AzShear provide a situational awareness of the strength of a couplet, it can also show rotational trends in a storm over time assuming that SAILS is turned on. Plus, the more sails the more information you’ll get in these plots. In the case above it appears SAILS2 was on as you’d get two leading signatures before the data merged back into one storm.

–FLGatorDon

Around 2120Z – interesting structure on a storm SE of KMXX.   Can see in Azshear – inflow from the south immediately ahead of the gust front.  However, behind this feature – can see an area of enhanced Azshear.  Question would be – how much would the PBL be worked over – cooled – and how might that influence tornadic potential?  Yet – another easy depiction on what is going on with storm evolution.

The single radar AzShear product continues to show utility in diagnosing storm structure and trends which leads to higher confidence and earlier warning decisions (in addition to the overall SA nature of the product).

In this case you can clearly see the line segment transition from (see captions):

— FLGatorDon

Not in this event – but would be interesting to note the trends in Inst AzShear for Sig Hail producing storms – e.g. mid-level mesocyclones.

Using a combination of Z, Zdr, inst AzShear from KMXX – can see development of low level mesocyclone quicker than V/SRM alone.  Can see the “white” > 0.01 s1 show up as early as 2000 UTC on the main TOR- while Z/SRM shows mainly a convergent signature.

Looking down the convective line – south of KMXX – examining the Azshear around 2040 UTC.  Area near the county border does trigger above 0.01 – whereas areas further south are slightly weaker (see image).  Would be interesting to know which of these produced tornadoes.  Reminder – plotting the tracks would be great!

First time looking at these products (Single Radar AzShear, Merged AzShear 0-2km, and Merged AzShear 3-6km) and I’m already liking how quick it is to pull my eyes to areas I should be paying close attention to. The most obvious feature is the circulation well to the SW of the radar site (close to 115km out), but what I find to be even more useful is watching mid-level rotation tighten into a low-level circulation closer to the radar site (around 51km away). In the first screen capture below, the Single Radar AzShear product highlighted the RFD bulging out, which is very useful in being able to fully diagnose the developing case. In an operational setting, having the full suite of AzShear products available to supplement traditional radar products could raise confidence when making a warning decision. Both of the merged products increase my confidence in the vertical depth of the circulation, but is also useful when diagnosing shallow circulations, at least in this one case I’ve been looking at. I’ll be interested to see how these products perform in other cases, particularly ones that involve the more shallow QLCS TOR-scenario.

All that said, I will say that there are enough false positives appearing in the AzShear product suite, particularly the Single Radar one, that caution should be taken if using solo, without reference to the traditional radar products. In an even more active scenario, I could potentially see false positives taking the warning forecaster’s attention away from features that need closer attention.

~Gritty

The AzShear products seem to accentuate features such as the RFD which could allow for a better assessment of RFD strength and the potential for new tornado genesis in cycling supercells.

In this specific example the initial tornado weakens or dissipates, and when faced with a decision whether to continue or re-issue a warning, the enhanced RFD signature would have prompted me to continue the warning. Sure enough, several scans later a new circulation developed that would have prompted a new tornado warning on its own.

— FLGatorDon

In a zoomed out view the AzShear products can draw your attention to small gate-to-gate signatures in velocity data that would be harder to see without zooming in. In the image below it’s hard to see the gate-to-gate, but the AzShear product is standing out for the northernmost couplet.

Now reference the zoomed in velocity:

Additionally, the MergedAzShear products can alert you to couplets that are occurring at low-levels nearer to other radars than are currently being viewed. For example, in CWAs with multiple radars and with limited screen real-estate due to performance and monitor limitations, it is impossible to view all radars at once. Thus you find yourself switching tabs a lot. Utilizing the MergedAzShear can tell you when you need to look at a different radar and which radar you need to look at so you can triage a storm as fast as possible. See merged product:

vs. a single RDA AzShear product:

And note the detail you can see in northern AL and western TN. After addressing the storms in eastern MS, I know I need to switch and look at nrn AL.

— FLGatorDon