Open epag opened 3 weeks ago
Original Redmine Comment Author Name: James (James) Original Date: 2020-02-10T11:44:02Z
Priority unclear. Will depend on feedback from Jason. I think the first priority is to get the thresholds in there (#74266) with some hook that is meaningful to a user, such as the declared name (e.g., "ACTION_STAGE"). I think this ticket is probably a second priority that can wait, but I'm not sure.
It is worth noting that, in the absence of a user-declared name for a threshold, this ticket is important not only to make the format self-contained but also to make the thresholds understandable to a user. The thresholds @{THRESHOLD_1,...,THRESHOLD_N}@ are ordered but, absent a user-declared name, a user needs to cross-reference a blob with, say, a @thresholds.csv@ to understand the output. That is obviously unacceptable.
Original Redmine Comment Author Name: James (James) Original Date: 2022-11-16T13:21:05Z
Reminded of this again today. It is basically impossible to interpret the netcdf statistics associated with thresholds because the netcdf contains no meaningful threshold information.
Author Name: James (James) Original Redmine Issue: 74738, https://vlab.noaa.gov/redmine/issues/74738 Original Date: 2020-02-10
Given a collection of statistics that vary by feature and threshold When I write netCDF blobs that contain those statistics Then I expect to see the thresholds that vary by feature
( Given a naming convention (#74266) where the N thresholds are named generically, {THRESHOLD_1,...,THRESHOLD_N}, then there should be an additional N variables in each netCDF blob for those N variables, each one containing the threshold values associated with all features. )
Related issue(s): #226 Redmine related issue(s): 75200, 75667, 85491, 109783, 110007