OCTANE

Have knots abbreviated as “KTS” instead of “KN”

Change direction of movement from to lettered degrees instead of a numerical value

This product does help me become more aware, in realtime of the winds vertically.  However, not entirely sure how to adapt this into my forecasting routine yet.

NUCAPS

Great to see the better sampling/readout of the data compared to what it was 2-3 years ago

The parcel count is a great way to help me gauge the validity of the data (confidence in how accurate it is)

Overlaying a NUCAPS forecast field with the parcel count allows me to sample what the field has and what the parcel count is so I can have more of less confidence in the data

No less than six hours for operational needs.  9 hours might be the perfect duration.  I usually don’t use hourly data much beyond 9 hours due to my lack of confidence in the reliability of the data.

Hourly data is very nice.  Half hour spacing is a bit too much data for that duration.
-Something to consider is could there be half hour spacing in the data for the first three hours?  However I don’t know if that would be enough of a benefit to use.

I would use the 700-500mb lapse rates, ML CAPE, temp and dew point, and parcel count most often.

PHS

Very easy to look at; very smooth data

Didn’t have much time to look at the data

Lightningcast

Noticed on a well defined supercell the lightning probability is not over 80% despite lightning ongoing.  Does the program cap at 75-80%?
-Have GLM ligthning data displayed too

Otherwise this does help draw my eye to where lightning could occur in the near future.

Prob Severe

Didn’t have time to look at it much. Did notice the storm in eastern CWA had higher values for version 3 than for version 2

– Rainman