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)

Steve H., Dave, and Jonathan had a lost hail contour around this time. It’s a known bug with the software.

Also, they are working six threats at the current time, and think that the management of the threat areas needs more automation (see previous entry).

Travis Smith (EWP Weekly Coordinator, 19-23 May)

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)

Comment from Steve H., Dave, and Jonathan (via Mike M.):

If the threat area seems to be advecting downstream with an acceptable motion, they would like to be able to just update the probabilities without worrying about moving the polygon (that is, the polygon moves by itself).

Travis Smith (EWP Weekly Coordinator, 19-23 May)

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

Kevin Manross (Gridded Warning Cognizant Scientist)

The team of Steve H., Dave, and Jonathan have been working the South Carolina storms in the Charleston area, along with Mike M. (probwarn coordinator). So far, they’ve been exclusively issuing hail and tornado threat areas. The cancelled the threat areas for the first storm as it moved offshore in the last 20 minutes. They may begin issueing wind threat areas as well as they begin focusing on a new storm.

We’ve had live streaming video from Charleston channel 5 for the duration of the event, although it hasn’t resulted in too much addition information about ongoing storms.

Travis Smith (EWP Weekly Coordinator, 19-23 May)

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)

There are several issues preventing SHAVE from keeping up with the storms of interest in order to provide real-time reports. Becaues the LSR’s are pretty timely today, we’ve decided to go ahead and collect high-density reports on the storms that the forecasters are focussing on although it will be delayed. This will let us do a nice comparison in post-analysis although it’s not really helpful for real-time decision-making.

Travis Smith (EWP Weekly Coordinator, 19-23 May)

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)