We have reached the end of a very successful first week at HWT. Today was a shorter day dedicated to the GOES-R focused 'Tales from the Testbed' as well as a weekly debrief. This debrief covered our activities from yesterday as well as a wrap-up discussion from the entire including topics like which products were used, how they were used, what we can take away from the experience, and what is the next step for the experiment products within in an operational setting. Check it out...
PGLM
- 'We were able to successfully issue a warning in Lubbock based only the PGLM and golf ball sized hail resulted from the storm.'
- 'The one minute update for the total lightning data is a huge benefit over the traditional radar updates.'
- 'There was a storm that barely reached 40 flashes and ended up dropping penny sized hail, so [the PGLM] was fairly successful in this case.'
Cloud Top Cooling
- 'We had upwards of an hour and a half lead time given by the CTC in the Lubbock/Amarillo area.'
- 'The product wasn't useful in areas were there was cirrus contamination.'
GOES-R CI
- 'There was a 97% CI hit on the storms in Lubbock and it was successful.'
- 'The CI is too noisy. THe 10, 20, and 30% values are just a little too much. Maybe it would be better to use values of only 50% and greater.'
- 'The strength of signal concept was good.'
- 'The instantaneous concept of the CI made the product less intuitive, it jumped around. Perhaps it would be better if it focused more on the trend (i.e. a consistently increasing strength of signal on a particular area of cu).'
- 'You could see some of the trend in the CI, but then it faded again. If this happens, as a forecaster you think maybe [storm development] isn't going to happen.'
- 'Some additional continuity would be nice... for example, giving a probability of convective initiation over a specific area at a specific time.'
Forecaster thoughts... i.e. how would do we integrate these into an actual operational setting?
- 'A lot of the experimental products a very useful, but for a warning forecaster their first instinct would be to look back to the base data. It seems that this data would be more useful to a mesoscale analyst, who has time to look at each product in detail.'
- 'It may be hard for a warning forecaster to be looking at the experimental data because there's just so much of it, especially when things are rapidly developing.'
- 'As a warning forecaster I do use some of the experimental data when I can, but don't always have tie to look at all that stuff. That would definitely be useful for a mesosscale analyst and share with the warning forecaster.'
- 'Our mentality is, warning are the most important thing, even in an experimental setting... so it's good to view these new products with that mindset.'
- 'The training had me comfortable with the products when we came in... learning how the interpretation various and also finding out how to work with the products together was a challenge.'
- 'I could see myself using all the products we used this week in an operational setting.'
- 'You have to incorporate the products into an operational mindset. Once you get more used to them it becomes easier, but it's definitely not an immediate process. It take time to become comfortable with them and figure out how exactly it can be incorporated into your own procedures.'
The discussion today, particularly regarding integrating these new products into current forecast operations, was very enlightening. Forecasters have their own mindset when issuing warnings, etc., and trying to integrate new products into this process is an interesting challenge faced by all in research to operations. However, testbeds like HWT are, I believe the stepping towards towards a successful R to O, and I look forward to continuing this effort next week.
See you then!