AzShear Artifact?

Collection of AzShear images from KLSX between 1818-1824 UTC. Values appear to “flash” from unrealistically high to low values (given background environmental assessment) over successive images.  No obvious DA issues in base data/velocity during this period. Radial range from KLSX was ~90-100 km. The most notable instance of this occurred to the southwest of the KLSX RDA. -QLCS

Smoother TORP with Highly Variable Max AzShear

With a storm in close proximity (~20 miles) to the KEAX radar, AzShear had some rather large jumps in maximum values. The data was pretty noisy due to the proximity to the radar, so the rapid change in AzShear makes sense in this case.

After looking at the base velocity data, it looks like to drop off of the max AzShear had to do with range folding or bad radar data close to the radar.  When the range folding affected the couplet pasing to the NNW of the radar, AzShear dramatically dropped off in response.

TORP also displayed various jumps as well in response to the variance in AzShear, but was way more tamed than the AzShear. This is good to see that there is not as much variability in TORP even with the jumps in AzShear as AzShear is the top parameter TORP relies on. This could be confusing if TORP jumps back and forth from 20% and 60% (just throwing out numbers), so it is good to see it’s more smooth than the jumps in AzShear.

-Stormy Surge

Slow TORP Response for TOR Warning Consideration Event

From 1500-1515 UTC,  a brief increase in organization and rotational increase occurred along a broad shear zone in Clay County, Missouri. Eventually, a rather pronounced cyclonic convergence signature appeared at the north side of the convergence zone, with TOR warning consideration made. However, despite prolonged period of critical AzShear threshold values met, TORP was slower to respond, and by time values spiked towards relative maximum (~65%) for this event, the signature had abated from a base data perspective. -QLCS

Transient TORP Object Amidst Weak Cyclonic Signature

Around 1445 UTC Tuesday, with evidence of weak cyclonic convergence from base data/KEAX (top), a TORP object (~40%) was generated. This occurred despite AzShear remaining below critical threshold. The cyclonic signature on base data/SRM weakened over subsequent scans, and the TORP object ended. In early days of the experiment, I have been using ~40% as a baseline threshold for TORP situational awareness. Will continue to assess if similar instances occur, requiring a shift in baseline TORP percentage.  -QLCS

Early Detection of Strongly Tornadic Event

With lead time of ~30 mins to a strongly tornadic event, Az/DivShear were exceeding threshold values, despite rather meager rotational convergence (mostly purely convergent) from V/SRM analysis (see above). This time (~1920 UTC) also corresponds with a large jump (~20 to ~50%) in TORP probability.  At minimum, the PHI products helped as a situational awareness tool to an evolving threat (rapid increase towards rotational convergence and significant tor-gen).

This is in strong contrast to a storm that later impacted portions of Allendale County, South Carolina about an hour later. A rather deep mesocyclone and at least weak (~15-20 knot VROT at 0.3-degree) rationally convergent signature was noted. However, TORP remained <30-40%. Will closely monitor how this tracks across a continuum of cases the rest of the week.   -QLCS

Merging TORP Objects in Two Close Proximity Storms

Looking at the TORP product, it seems to have combined tow storms in close proximity into one object. The scan before on KCLX and the scan after had two object for each storm, but in this scan in particular, the two were combined into one. It is good that the algorithm made it a brand new object as oppose to a continuation of one of the prior objects. This makes sure the object history is accurate when it goes back to identifying the two as separate objects in the object history.

Satellite HWT Day 4 Carl

Satellite HWT Day 4 Thoughts

Octane Direction

During my initial afternoon analysis I noticed a good use case for the directional product in identifying how different air masses may be coming together over the CWA. In the directional product below, we can see the magenta showing the moist surface air mass that is advecting up from the SE into west Texas and western NM. A drier air mass that is creating a bit of a dry line is pushing from the west in the more yellow colors, with some glaciating cu noted within the Day Cloud Phase RGB. Elevated convection that is still persisting from overnight can be see pushing to the southeast in the lower right, giving the more green colors. This provided a very clear and quick way to pick out these different air masses that will be the main players later in the afternoon for potential convection.

MoistGradConv RGB ECONUS

Some really interesting features that stood out when looking at this imagery during the afternoon today. Notice the sharp gradient in the light vs dark greens running across Texas, starting in the southern pandhandle near the NM border and then running SE through central parts of TX. When overlaid with 24 hour MRMS precip, you can see a clear boundary between the areas that received rain last night (the panhandle, darker greens) and the area that did not (lighter green in the Big Bend areas). This clearly stands out in the Snow/Ice NIR band which makes up a portion of the RGB. Moisture can also be seen pooling in west Texas as it moves northwestard along the edge of the Mexican Plateau. Obs later in the day showed that the “brighter” area was mixing out a bit faster given the lack of soil moisture. Some good potential situational awareness being combined within the RGB, given the ability of this to also pick out things like the dry line a little bit easier.

ProbSevere v3

Issued a warning in an area of pretty poor radar coverage (lowest tilt height was around 15kft). MRMS was still capturing a good bit of the freezing level to -20C isothermal levels, so ProbSevere was running pretty strongly with hail probabilities. Additionally, there were some significant bursts of cooler cloud tops, and the Octane product began to show some of the stronger “divergent” signatures that we had seen throughout the week as well as highlighting a clear AACP, all signs of a stronger updraft capable of keeping hail lofted.

Given the environment, these products definitely gave me additional confidence and potential lead time, given these cores really grew tremendously about 15 minutes later, including an eventual split and right mover that likely produced some large hail (hard to verify in this area given lack of population).

More Octane (Speed)!

Another picture from later of how this storm grew and exploded. Octane was showing yet another AACP. A very interesting feature of this is that Octane speed algorithm does seem to be “tracking” the AACP in a way. There are a lot of research groups out there that have been looking at ways to track these features for injections of tropospheric moisture into the stratosphere among other things, so this could be a novel way at looking at that problem.

An hour or so later, we can see how the Octane product can be used to see that a storm was weakening. The deep blue divergent signature began to quickly fade, an indication that the updraft wasn’t as strong as it was previously. Given this is data flowing in from the mesoscale sectors on GOES 16, we are getting one minute updates, which will give some lead time over analyzing the core of the storm via the radar or MRMS which needs to get the radar data and then process it. This can be important for SVS or considerations for a downstream severe. I ended up still issuing a downstream severe, but was able to use what I was seeing in the product with the weakening trend to decrease the expected hail size. MRMS and ProbSevere trends closely followed, moving downward in severity.

Above: Weakening trend starts around 22Z for the Octane Speed product in the top left

Below: ProbSevere and MRMS trends begin to come down around 22:05Z or so, lagging the above by a few minutes. Every minute counts in lead time.

-Carl Coriolis

Tags: None