Dave is paying close attention to the “upper-level” tilts (~3.1 deg) and is issuing his polygons from here. Not that this is wrong by any means, but not an anticipated procedure. We’ll see how it goes.

Also, still having some struggle with issuing new warnings – kinda clunky, plus awfully easy to mix up warning attributes between warnings.

Finally, Dave and Ryan opted to issue a larger warning polygon to cover two threats instead of two smaller ones.

Kevin Manross (Gridded Warning Cognizant Scientist)

Software issue(s) – had a crash of wg when we deleted the Edit Polygon window, but the checkbox was still checked. He clicked it off and then back on and the display crashed.

When he brought the display back up (save setting shortly before – yea!), the shift-arrow browsing didn’t seem to work correctly. It wouldn’t go up to the “old” elevation. I have experienced this before since the latest fix by Charles. Not sure if they are related, and I’m not implying that as this might be an issue with having an incomplete volume scan.

In the meantime, we’ve issued another warning.

Stay tuned…

Kevin Manross (Gridded Warning Cognizant Scientist)

Alrighty, sitting with Dave and Ryan as they are focusing on a storm in the CYS area, specifically a storm to the N of KCYS with marginal hail signatures.

Kevin Manross (Gridded Warning Cognizant Scientist)

Removed TOR threat as things look to be moving toward a wind threat. However, we’re analyzing any QLCS TOR threat…

Kevin Manross (Gridded Warning Cognizant Scientist)

Ryan and Steve switch off again. Looks like our newest TOR threat is outrunning the storm.

Kevin Manross (Gridded Warning Cognizant Scientist)

New storm developing ahead (SE) of our current storm developing on converging surface boundaries. Steve has been resistant to issuing a new warning on this because it is covered by the swath from the upstream storm.

Discussion ensued regarding how this best should be handled. Steve recalls a storm-based warning where two adjacent areas were warned on several minutes apart and received complaints that the users in the broad area were already warned, why are they getting it again?

Ryan suggests that these are different storms, with different probs and different times of arrival. Steve agrees to issue a low-prob broad area for the new storm.

Kevin Manross (Gridded Warning Cognizant Scientist)

Steve comments on workload again – this time mentioning that even without the PROBWARN type of exercise, offices are even now going to a “warning manager” and an “analyst”. This exercise would certainly extend that trend.

Steve also asks “what happens if/when swaths from differing storms overlap? Each gridpoint would have attribute info from any swath that affect that point.

Steve also suggest that a “preview window” would be nice since he didn’t want his swath to go as far as it did.

Kevin Manross (Gridded Warning Cognizant Scientist)

Steve mistakenly changed threat type of his wind warning to TOR. He switched it back.

Kevin Manross (Gridded Warning Cognizant Scientist)

Steve expresses concern about workload with multiple threats on same storm.

Kevin Manross (Gridded Warning Cognizant Scientist)

Steve and Ryan switch off, with Steve now drawing the warnings. He deleted/canceled the warnings on the NErn storms du e to decreasing MESH and getting behind the sfc boundary.

Steve asks – how will cancellations be handled?

Reworking the SWrn storm’s hail threat.

Kevin Manross (Gridded Warning Cognizant Scientist)