Week 5 Summary and Feedback (8-12 June 2015)

The final day of Week 5 and the 2015 Spring Experiment took us to the Boulder, Topeka, and Omaha CWA's. The Boulder group had ample opportunity to evaluate the PGLM total lightning products. As with the previous several days, the 1-min satellite imagery from GOES-14 was available over the areas of interest and utilized extensively by participants.

- Bill Line, SPC/HWT Satellite Liaison

GOES-R LAP
- Best to pay attention to gradients, the absolute values weren’t that accurate (for CAPE)
- Higher temporal frequency will be appreciated in goesr era
- Various use cases (convective, flooding, winter, etc.) of how these products can be applied in operations would be helpful to see in training

NUCAPS
- Improve training to present how to use, include more information on editing lower levels, including info on how high to mix
- I prefer to look at rap, even though its model data, because it shows me the fine details that NUCAPS does not capture
- Fusing of all the sources is really the way to go, they should all be blended together, instead of having to use them all

GOES-R CI
- I liked using it this week, but  I would want it to work better under thin cirrus
- I remember looking at it a few years ago, and it’s a lot better now than it was then. It provided useful information before event.
- When you get constant rapid scan, it will be available more timely, more often, which will certainly help
- Seeing it overlaid with more in awips would be great. I look at it on webpage now
- For cwsu it will be especially useful, seeing signals will lead me to start the alert.

ProbSevere
- It has its flaws, so people need to know these, must be in training.
- I could see us using that on air, people understand percentages
- I almost view it more as SA type tool; stick with base data as gold standard for warnings,
- On busy day, I could see it being useful, have it up on radar or sat, for SA
- Have something/fields to get at low-topped convection
- Perhaps regionalize probsevere – train dataset on a local area instead of whole country
- Storm motion information could help – eg. acceleration before wind damage
- Someway to prevent the merger with linear storms, perhaps track at higher dbz once storms mature.
- If polygon gets over a certain size, throw in a new threshold, pick out cores within line
- Dbz at a certain temperature  level might be useful input

SRSOR and 1-min OTD
- TV viewers would love to look at that.
- Especially useful when debating on issuing another warning downstream, if you could see another updraft coming in, might help to issue or not
- Outflow boundary interaction could clearly be seen
- Low stratus movement, lake and ocean breezes.
- In san fran with stratus – It would help with aviation, timing of amendments knowing exactly where edge of stratus is asap is important
- I would see us using it all the time. West coast wild fires, any hazardous material.
- This could lead to more project ideas, discovering more ways to utilize data
- Want srsor all day every day
- Will always be necessary somewhere in the US

Lightning jump
- We were seeing very large sigma jumps.
- Showed significant jumps with strengthening storms
- More useful over high terrain, where radar coverage isn’t as good.
- I would like it to include a readout of the number of flashes that it jumped.
- Will be good to include this information in probsevere
- Area in cwa with bad radar coverage, something that is nationwide would be great, nice to see in these data void areas

PGLM
- Provides good SA, shows precisely when storms pulse up and down.
- Definitely will be helpful for DSS events. Someone deployed, they can track lightning activity