Overview: Week 1, Day 3

10AM

Day three kicked off with a loaded discussion, with OCTANE, Synthetic GXI Imagery, and the Lightning Stoplight Tool taking center stage. One interesting topic came from the presentation of Lightning Stoplight, and how to interpret regions with no data next to pixels in the 0-10 minute range (red). Would a site manager interpret that area as ‘safe’? This also led into a discussion on how forecasters would present these data to partners, with most in the group stating that they wouldn’t feel comfortable giving the Lightning Stoplight or LightningCast tools to EMs without considerable on-site guidance or training.

The forecast discussion was split four ways between Texas, Mississippi, West Virginia, and Colorado. We ended up going to the San Antonio, TX (EWX) office for a supercell and large hail threat, and the Charleston, WV (RLX) office for widely scattered convection with a marginal wind and hail threat. Forecast groups were also now tasked with two mock-DSS events, forcing them to monitor multiple events on the LightningCast superdashboard product. The Lightning Stoplight tool was not in AWIPS until 21 Z, but forecasters were advised to use the web display from NASA SPoRT.

1PM

I started the day by going west to Hawaii to collect SZA imagery at sunrise from GOES-West and sharing these with the forecasters. How much more ‘usable’ information can SZA provide compared the traditional imagery, and how much sooner if possible?

4 PM

After several discussion regarding DSS, LightningCast, and how to interpret the Synthetic GeoXO Imagery, we were able to get the Lightning Stoplight product into our AWIPS-II! Forecasters stated in the morning discussions they want to immediately union these data with LightningCast, and some procedures were made to help them out at the beginning of ops tomorrow. I created an animation of the Lightning Stoplight that includes GLM, ENTLN flashes, and ABI Clean-IR imagery. I set the opacity of the Lightning Stoplight to 80% so the colors stand out, but you can still see some detail underneath. We’ll see how well the forecasters like this information and if they make any new displays. This animation shows the dissipation of a thunderstorm on the western side of the scene, and you can see the loss of GLM FED data, while the Lightning Stoplight product changes colors and shrinks in size to indicate a decreasing lightning hazard.


The day ended with a quick look at sea-breeze thunderstorms in eastern Cuba for the SZA imagery. Its interesting to see the low clouds and how long they stay present in the SZA’s modified DCPD RGB. We’ll see how the forecasters like this in the morning.

 

Kevin

Tags: None

Tuesdays HWT

Main issue today was to do IDSS near Delhi MS. We were using lightning cast and lightning stoplight. We were also issued a few warnings. Fortunately, we had a storm move over the region so we were quite busy for at least an hour or so.

Our team created some loops of the data. A long loop of GLM and ltg prob is below …

 

 

 

The blinking circle was our DSS site. Lena was our “emergency manager” for the day.

We had thorough conversations with Lena and Kevin regarding using the tow lightning products in operations. We agreed that the products are very useful, but would not work all that well to send these products directly to our partners.

Note that we had a thorough conversation on the slack channel and you can follow the “blow by blow” discussions there.

We also had a great conversation with Lena regarding how we interact with our emergency managers.

Regarding Lightncast, I believe that the planview products are good. I prefer looking at the imagery like this though >>>>

 

Note that the data probabilities on the awips image above go from 0% to 100 percent.  Why is it important to show the data this way instead of contours? The reason is you can see the VERY beginning of when the ltg probs start to show up. Using contours, you have to wait until the 10% prob shows up. Note that I do not have sat pix imagery overlaid, The reason why I do this with AWIPS is I can have the sat pix data opened up in another panel and use the cursor to read the data. Also the contours (or the image for that matter) would get “lost” (or buried) within the colors of the sat pix imagery.

We used the Lightning Stoplight product today. This was helpful in letting us know when the last flash occurred in the 10, 20 and 30 increment time frame. However I am hesitant with sharing this directly with the EMs.

I envision that the Stoplight product and the LightningCast product will be married in the future, and this will make these two products more useful.

I can not say enough how valuable the lightningcast product is. Prior to this we did not have a good idea when lightning would be a threat, and would have to carefully watch radar data and do cross sections or monitor to -10C level. With lightningcast, you have the probabilities calculated for you in real time every minute (mesosector) or every 5 minutes for CONUS.(However waiting 5 minutes is wayyyyyyyy toooooo lonnnnnnnnnnnnng.

We talked about the SZA product. This is a no brainer and this satellite product should be implemented operationally as soon as possible. Being able to see the detail in the sat pix data towards sunset is priceless.

-Mesovortex

Tags: None

Big Ol’ Storms, Amazing Satellite Products!

Today’s focus for my group was over WFO FWD where discrete supercells developed, eventually congealing into a more linear storm mode. Being on the DSS desk today, I primarily used lightning products today, though I did peep at a few others. I wanted to take a moment to highlight the GeoXO 5.15/0.91 products for very clearly defining a moisture gradient over northeast TX that would eventually go on to be our focus point for CI.

Figure 1: WV/WVT/Itob/VISob Compare highlighting distinct moist/dry boundary

LightingCast:

Provided DSS using LightningCast V2 overlaid with OCTANE CONUS CTC. I really like using the products together as the increasing LightningCast probs nudge me to either contact or not contact an EM. Overall, I thought the product did very well. I did notice something odd in the dashboard that I spoke with the developer about – instances of GLM flashes were observed at a time there was a downward trend with LightningCast. Figure attached below.

Figure 2: LightningCast V2 vs V1

For documentation, here was the primary procedure I used today to make decisions:

Figure 3: OCTANE CONUS CTC w/ LightningCast (yellow circle is 8-mile radius DSS event)

Using all of the above mentioned products, here was a CWA graphic I put together:

Figure 4: DSS graphic

Feedback for Day 2

LightningCast: For the Dashboard, I feel like V2 did a better job than V1. The amount of variables being measured is a little confusing, and over time, I noticed I was more just looking at a trend rather than all of the different variables.

Stoplight: Though I never got to give the all clear for my DSS event, Stoplight matched up very well with LightningCast and radar trends.

OCTANE: Made some progress in terms of understanding some of the OCTANE products today, thank you for answering all of my questions, Jason! I really liked that we had 2 live weather events to compare the difference in the wind profiles with OCTANE. Yesterday, we observed a lot of greenish hues, indicative of stronger low-level flow. That element was a bit more lacking in FWD today, and the imagery corroborated that with more blue hues. Jason also showed us examples of cloud top divergence, with more blue/green colors indicating deceleration. After getting to know these products a little better today, I feel less overwhelmed by it.

GeoXO: I continue to be very impressed with this product’s moisture and boundary detection. The example I shared above was very impressive and mostly lined up with the 00Z HRRR.

SZA: Did not look at SZA today

-simoom

Tags: None

April 28th Hazmat DSS

Warm Sector Growth: Jaxson MS

The day started this morning with thunderstorm development from the overnight outflow boundary that remained in the southeast. This was quickly replaced by 1500 to 2500 j/kg of MUCAPE. There was 40 kts of shear, which would help to sustain any pre-frontal convection. With dewpoints in the warm sector approaching 75° in Northeast Louisiana. A very shallow cap was present, but quickly eroded from solar heating. Once the cap was eroded we got rapid growth of a thunderstorm complex. This complex moved slowly across Northeast Louisiana and Central Mississippi throughout the afternoon.

DSS operations for a Hazmat: Northeast Louisiana

We coordinated with a hazmat cleanup site that was near the Louisiana/Mississippi border. The emergency manager had required the heads up on lightning within a 10 mile radius of the location. In the figure below we see a developed thunderstorm complex that is moving west to east across the segment of the 10 mile radius. The OCTANE product allowed us to build confidence on a strengthening thunderstorm near the hazmat clean up area. We can see a very moist inflow on the southwestern edge of the complex. It was good that we were able to see a very distinct inflow because we received a report of 1.75” hail. This inflow allowed the thunderstorm to continue to strengthen.

Cessation of Lightning:

The biggest question the public or our partners will ask, is when will the lightning end. We used a variety of tools to determine when it is good to give the all clear. They were the lightning stoplight, lightning cast, and radar. With this event we heavily relied on the stoplight and radar, due to a lag in the lightning cast probabilities. While lightning cast had identified lower chances it would still put over 50% probabilities when the threat had been over for 30 minutes.
The first graphic shows a quick downward response to the cessation of lightning. However, on the second graphic we see lightning probabilities remain elevated for a long period of time. Using other tools like lightning stoplight and radar, it makes no sense that we should be holding the all clear until the probabilities go near 0. While lightning cast may not be perfect, it is another tool in the toolbox.
-Blizzard
Tags: None

Lightning Cast V1 vs V2

LightningCast version two highlighted an area of towering cumulus as having a greater probability of producing lightning when compared to version one (30% vs 10%). Later on, version one caught up with version two, highlighting the same area, with both versions increasing to 70% (not pictured). However the signal showed up well in version two about 20 minutes ahead of version one.

Figure 1: GOES flash extent density, 1-min lightning plot, cloud phase distinction, and Lightningcast v1 (left)/ lightning cast v2 (right). Valid at 1930 zulu

Figure 2: GOES flash extent density, 1-min lightning plot, cloud phase distinction, and Lightningcast v1 (left)/ lightning cast v2 (right). Valid at 1950 zulu.

-WXboi

Tags: None

Overview: Week 1, Day 1

9AM

Welcome to the testbed! Day 1 is usually when forecasters are just getting their feet wet with the products, but today they may get thrown into the deep end. The 13Z SPC Outlook features a Moderate Risk and large Enhanced-Slight Risk through the Mississippi Valley, driven by a 15% CIG2 threat. Forecasters will mostly be getting familiar with products and using AWIPS in cloud instances, but hopefully they will have plenty of good storms to observe today! Unfortunately we’re having issues getting the Lighting Stoplight tool into AWIPS, and it was only available online today.


1PM
We localized to Paducah, KY (PAH) and St. Louis, MO (LSX) with the expectation that semi-discrete thunderstorms would develop during our operations period. Unfortunately thunderstorms took too long to develop for PAH, but there was plenty of thunderstorms to the west across Missouri and north towards Illinois and Indiana.

We observed low level dry air from the Synthetic GXI data from a front and dry line that passed through western Oklahoma. It was interesting to compare the synthetic data from WVT and low(est) level water vapor at 5.15 µm against the observations from GOES-R in the split window difference and visible imagery at 0.64 µm. Some questions for the forecasters included how easy it was to identify features and boundaries in this clear-cut and more strongly forced scenario.

4PM

Later in the day our group also had a discussion about extremely large flashes as detected by GLM and the ground networks, and how (or if) they could be interpreted by products such as LightingCast or the Lighting Stoplight tool. Could LightningCast add lower probability contours? Would those contours add to noise and too many false alarms? How sensitive should users be to the appearance of probabilities?

6PM

To end the day, I saved off some animations of the SZA products. I tried adjust the Day Cloud Phase Distinction RGB recipe when including the Channel 2 and 5 SZA bands, so we will see how forecasters react to that product.
Kevin
Tags: None

Day 4- Large Hail in Texas

Conditions were favorable for severe thunderstorms across west Texas on Thursday, June 5, 2025. High instability and shear led to rapid development thunderstorms across the high plains. Initially, a cluster of thunderstorms congealed into one which then split into two. The right mover went on to produce at least 3” in diameter hail and wind gusts in excess of 72mph. Due to the poor radar coverage in west Texas, GREMLIN was useful in supplementing radar and MRMS data. GREMLIN showed features I hadn’t seen in the start of the week, including bean-shaped storms and double updrafts that later split into two storms.

GREMLIN had some odd things occur too. ECONUS GLM did not represent the lightning that was occurring with these storms and it is believed that this may have degraded GREMLIN.  In the loop below, ECONUS GREMLIN produced a fictitious cell northeast of the left and right movers. It also lagged a bit before it showed two strong cells, especially the southern storm.

Four Panel-GREMLIN EMESO-1 (top left,) MRMS -10c (top right,) GREMLIN ECONUS (bottom right,) and CH07 (bottom left.) In this example you can see the stronger storm to the south

Here is a single image of the bean shaped cell that produced at least 3” hail.

LightningCast was useful for situational awareness and messaging our partners for the DSS event. We noticed V2 was a little better at maintaining the high probability of lightning (greater than 90%) than V1 in mature convection.

LightningCast proved to be useful for our fictitious DSS event in west Texas. V2 was faster to increase the probability of lightning prior to lighting occurring at the event (below.) It was also faster to show lightning cessation. There was a brief lull in lightning mid-way through the operational period and both V1 and V2 showed about a 20 min lead time of the probability of lightning decreasing in the next hour. V2 stayed slightly elevated compared to V1, but both highlighted that there was still a high probability of lightning in the next hour.

Lastly, OCTANE (below) proved to be useful again in warning operations. Robust, mature convection was ongoing and while it was “off to the races” in west Texas, the speed and divergence products continued to the tight gradient of speed divergence. We noticed that the compressed color scale was more “eye catching” to show the tight gradient. Below is a picture of the speed/direction divergence product with sampling turned on. The overshooting top was at an impressive -85C with winds out of the west at 50 mph. In this example, the gradient on the west side of the storm helped maintain our confidence of a powerful storm.

– Eagle

Tags: None

Supercells in Southwest Kansas

 Convection crossing into Hamilton County

Pretty much right at the start of operations, convection over southeast Colorado began pushing east into Hamilton County, KS. Looking at the first gif below (Figure 1 with the Octane 4-panel), you can really see a persistent divergence signal as the storm continued into the county. Additionally, probsevere (located in the top left panel) was pretty high, maxing out above 90%. Next, looking at the LightningCast panels in Figure 2, you can see the lightning jump occurring right as it crosses over the county line. Utilizing these products together and noting radar showing a mid-level meso with 50 dBZ over 35kft, we felt confident to go ahead and issue a Severe Thunderstorm Warning for this cell (shown in Figure 3).

Figure 1: Octane 4-panel with ProbSevere overlaid in the top left panel

Figure 2: LightningCast v1(left) and v2(right) with GLM

 

Figure 3: Radar Reflectivity with the Severe Thunderstorm Warning

 

GREMLIN (top left panel in Figure 4 below) did a pretty good job showcasing this cell, as well as another strong cell just to the southwest, however compared to MRMS (top right panel), it didn’t capture the stronger reflectivities as well, and was approximately 5-10+ dBZ off. So if I didn’t have radar access and could only rely on GREMLIN, I may not have felt as strongly about issuing a SVR.

Figure 4: GREMLIN 4-panel

I didn’t grab images of this, however later on, there was a clear decrease in the lightning activity, with noticeably lower divergence and cloud top cooling. This gave me the confidence to cancel my warning early.

Octane and ProbSevere

Later on, the same cell over Hamilton County began slightly cooling again, with ProbSevere noting 59% probabilities (top left panel in Figure 5). Additionally, there was a very clear mesocyclone noted in Figure 6. Using just these two products, I may have been inclined to issue at least a SVR warning. However Octane wasn’t noting much, if any, cloud top divergence or cloud top cooling. Lightning also didn’t look very impressive either. Noting this, I strayed away from any warning issuance (especially considering radar was sampling this storm at 12.5kft), which I think was a good call, at least for this time.

Figure 5: Octane 4-panel with ProbSevere overlaid in the top left panel

Figure 6: Storm Relative Velocity

LightningCast Dashboard for the DSS Event in Dodge City

Closer to the end of operations, the LightningCast dashboard (Figure 7) started showing higher probabilities of lightning, with the Max prob for a 10-mile radius showing 77%, v1 at 45%, and v2 at 30%. There were two supercells several counties west of the event that were expected to track southeast, missing the venue, however with the dashboard and CAMs showcasing the potential for lightning to reach the event, we were confident enough to fill out a DSS form and graphic (shown in Figure 8) with this information.

Figure 7: LightningCast Dashboard

Figure 8: DSS Graphic
It should be noted that v2 only highlights a 30% probability, and later on was ~44% lower than v1 (v1 was at 76%, with v2 at 32%. With this being at the end of operations, we couldn’t see if lightning actually occurred at the event, but I’d be interested to see if v2 actually had a better grasp on the convection tracking southeast and missing the event altogether, or if v1 showcasing the higher probabilities was the better option.
Final Thoughts from Day 4:
The Octane product really shined today, both in increasing my confidence to issue a SVR warning, and in talking me down from issuing a separate warning. I’ve been sold on the Stoplight colorcurve, with no smoothing (top right panel) coming out on top.
– Fropa
Tags: None

Nowcasting Convective Initiation and Evolution with OCTANE, GREMLIN, and LightningCast

SYNOPSIS – A remnant outflow boundary from previous convection was laid out across portions of west Texas. Heating and destabilization occurred along this boundary, setting the stage for scattered supercell development where convergence was maximized. Below are some observations and notes regarding data seen in OCTANE, GREMLIN, and LightningCast.

OPERATIONAL NOTES AND FEEDBACK – Nowcasting Convective Initiation with OCTANE and LightningCast.

As is so often the case in setups like this, there was a fairly large area of towering cumulus clouds and occasional attempts at convective initiation (CI) along the outflow boundary. For today’s operational period, I tried a 4-panel combination that included OCTANE products, LightningCast, and traditional satellite imagery (Figure 1).

Figure 1 – OCTANE Speed (top left); OCTANE Cloud Top Cooling/Divergence-no smoothing (top right); OCTANE Cloud Top Cooling/Divergence-medium smoothing (bottom left); VIS/IR Sandwich + LightningCast (bottom right)

As was seen in previous days of this experiment, OCTANE products helped to identify areas of towering cumulus that had the most vertical growth and, consequently, the greatest near-term potential for CI. This is evidenced by the green shading in both the OCTANE Speed and OCTANE Divergence products in Figure 1. One of the potential enhancements to nowcasting CI is LightningCast. While OCTANE appears to excel at depicting where towing cumulus has the most vertical development, LightningCast appears to excel at pinpointing which of those areas of more developed cumulus have a better chance at producing lightning. This essentially provides additional probabilistic information for trying to determine where CI may soon occur, which trickles down to knowing where to focus pre-CI IDSS.

In Figure 1, for example, an increase in lightning probabilities was observed just west of the WFO Lubbock forecast area, where OCTANE was highlighting increased vertical development of towering cumulus clouds. The increase in probabilities, plus consistently high probabilities, provided lead time on where CI would eventually occur. Note the consistently high probability of lightning in that area, as well as increasing probabilities to the south. Two separate supercells eventually developed in this area, and later went on to produce severe weather.

OPERATIONAL NOTES AND FEEDBACK – Nowcasting Convective Evolution and Intensity with GREMLIN.

For today’s operations, radar coverage was not a challenge, but GREMLIN data was still analyzed to determine if there is utility even in cases where radar coverage is sufficient. Today’s event highlighted several important observations about GREMLIN.

1) This is the first event during this week’s experiment in which 60+ dBZ echoes showed up on GREMLIN. This closely matched the 60+ dBZ cores seen on MRMS (as shown in Figure 2 below). It was noted by the developers that 60+ dBZ echoes offer a high likelihood of severe thunderstorms and this was, indeed, the case in today’s event. This suggests that GREMLIN may offer increased confidence in the occurrence of severe weather regardless of good or poor radar coverage.

 

 

Figure 2 – GREMLIN Emulated Reflectivity (top left); MRMS Reflectivity (top right)

2) For sustained, deep convection with cold cloud top temperatures and lightning in the anvil, GREMLIN may sometimes erroneously equate this to precipitation occurring at the surface. Note in Figure 3 below the area of 40+ dBZ echoes depicted by GREMLIN over the northwestern part of the Lubbock CWA. This area corresponds to nearby GLM lightning, but note that no precipitation is depicted by MRMS reflectivity or WSR-88D reflectivity (not shown).

3) When thunderstorms are close together with merging anvils, be aware that GREMLIN may treat this as one thunderstorm, instead of multiple thunderstorms, as seen in Figure 3. Note the one cell seen in GREMLIN data near the far western edge of the Lubbock CWA, then compare that with the two cells that actually existed (as seen in MRMS data). It should be noted, though, that GREMLIN did well to capture the most dominant of the two thunderstorms.

Figure 3 – GREMLIN Emulated Reflectivity (top left); MRMS Reflectivity (top right); GLM Lightning (bottom right)

OPERATIONAL NOTES AND FEEDBACK – Nowcasting Updraft Strength with OCTANE

Today’s event provided an interesting opportunity to nowcast two strong updrafts in close proximity to each other. In Figure 4 below, the OCTANE Speed product reveals a strong updraft developing within the divergent area of a nearby thunderstorm’s updraft. The developers noted that this is impressive because essentially the former updraft is strong enough to oppose the already enhanced, and modified, flow around the latter updraft, suggesting an increased risk of severe weather. The OCTANE Speed product appears to better depict what is happening to the flow aloft around both updrafts when compared to the VIS/IR sandwich product alone. I suggest using OCTANE and the VIS/IR sandwich product in tandem with each other when nowcasting convective updraft evolution.

Figure 4 – OCTANE Speed (top left); OCTANE Cloud Top Cooling/Divergence-no smoothing (top right); OCTANE Cloud Top Cooling/Divergence-medium smoothing (bottom left); VIS/IR Sandwich (bottom right)

– NW Flow

Tags: None

Southwest Texas Lightning Product Performance

Lightning, and GOES-East vs. GOES-West

Observation 1: GLM discrepancies between satellites

Left: GOES-East LightningCast v1 & GLM FED        Right: GOES-East LightningCast v2 & GLM FED 1836 UTC – 1931 UTC 5 June 2025 in southwest Texas

GOES-West GLM 1911 UTC – 1933 UTC 5 June 2025 in southwest Texas (LightningCast outside the domain)

The Midland-Odessa (MAF) forecast area (and nearby upstream areas in Mexico) sits in a weird position where it is well within the GOES-East CONUS domain, but on the edge of the GOES-West CONUS domain (and thus outside the CONUS LightningCast domain), yet within the GOES-West full disk domain. The above images show GLM observations in southwest Texas from both satellites, where GOES-East shows far less lightning (and a downward trend) while GOES-West showed significantly more lightning at the same time (also with a downward trend, but still indicating a stronger storm).

 

Observation 2: GOES-East LightningCast performance within areas where GLM FED is underestimating

 

While LightningCast data is not available from GOES-West in this portion of southwest Texas to compare GOES-West v1 vs. v2 as well as East vs. West, the quality of the GOES-East LightningCast product in areas with potentially degraded GLM observations raises an interesting question about how the models perform in this situation.

In the first GOES-East LightningCast loop shown above, version 1 and version 2 generally seem to perform very similarly, likely because of poor radar coverage and data availability. (See RQI image for the area below). Version 1 picks up on a contour of 70% ProbLightning for a developing storm to the northwest of our main cell at 1856 UTC, roughly the same time as Version 2, giving roughly a 20 minute lead time, with the first strike via GLM around 1916 UTC. Version 1’s 70% contour is larger and remains larger than version 2 for the first 10 minutes or so, before both products begin matching closely around the time of first lightning detection. Version 2 then quickly begins downtrending on that cell, seeming to pick up on lightning cessation prior to version 1 does.

Observation 2.5: GOES-East LightningCast DSS Dashboard

This storm impacted our DSS event. At 1955 UTC, DSS was provided to the partner that “lightning will be within 10 miles of the event within the next 30 minutes (by 2030Z) from a storm roughly 30 miles south-southwest of the location (the larger, southernmost storm in the GOES-East loop), a Severe Thunderstorm Warning has been issued for that storm just south of them but the warning doesn’t encompass the event, and that additional convection is going up north of the event, which may also bring lightning within the 10 mile range of the event.”

GOES-East LightningCast DSS Dashboard.

The decision to contact the partner about the DSS event at 1955 UTC was made with the help of the LightningCast DSS Dashboard, which had a max probability of lightning within the 10 mile radius of the event at 90% at the time of the contact. They were told they had less than 30 minutes before lightning was within 10 miles, and 20 minutes after that call, the first GLM strike was observed in that radius. Negating the time it took to fill out the DSS form online in comparison to picking up the phone, the DSS provided to the partner based on the dashboard output was 10 minutes late on onset, but could have been spot-on if the DSS call was provided immediately after the 10-mile radius probability reached 90% instead of waiting to see persistence before calling the partner.

Back to observation 2: GOES-East LightningCast performance within areas where GLM FED is underestimating

Also in the GOES-East LightningCast loop, there is a lower probability contour in the farthest northwest corner of the image at the beginning of the loop. Both versions pick up on it, and both versions go back and forth between characterizing this small bullseye area as continuous/connected to the two storms to its southeast and discrete. Version 2 indicates 50% probabilities briefly, while Version 1 does not. Both have probabilities dropping <10% at the same time, and lightning was never observed.

MRMS radar quality index

– prob30

Tags: None