Ensemble-Stat runtime error when obs_thresh <= CDP10 results in 0 pairs being used.

[JohnHalleyGotway]

Describe the Enhancement

Binbin Zhou from NOAA/EMC pointed out a runtime error he is seeing from the Ensemble-Stat tool. He is applying multiple obs_thresh filtering options, as shown below:

obs_thresh = [ <=CDP10, >CDP10&&<=CDP20, >CDP20&&<=CDP30, >CDP30&&<=CDP40, >CDP40&&<=CDP50, >CDP50&&<=CDP60, >CDP60&&<=CDP70, >CDP70&&<=CDP80, >CDP80&&<=CDP90, >CDP90 ];

However, Ensemble-Stat exits with the following error message:

DEBUG 2: Processing gridded verification HGT/P500 versus HGT/P500, for observation type ANALYS, over region TRP, for interpolation method NEAREST(1), using 2448 matched pairs.
DEBUG 3: Using 0 of 2448 ensemble pairs for observation filtering threshold <=CDP10.
ERROR  :
ERROR  : RPSInfo::set(const PairDataEnsemble &) -> no thresholds provided to compute the RPS line type! Specify thresholds using the "prob_cat_thresh" configuration file option.
ERROR  :

Since 0 pairs survive the obs_thresh filtering of <=CDP10, I would guess that Ensemble-Stat just isn't handling this degenerate case correctly. Need to replicate this behavior, add more checking, and prevent this error condition from occurring so that Ensemble-Stat can run to completion.

Time Estimate

2 days

Sub-Issues

Consider breaking the enhancement down into sub-issues.
No sub-issues required.

Relevant Deadlines

None

Funding Source

None

Define the Metadata

Assignee

• Select engineer(s) or no engineer required: John Halley Gotway
• Select scientist(s) or no scientist required: John Optaz

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Review projects and select relevant Repository and Organization ones
• Select milestone

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdb, METviewer, METexpress, METcalcpy, METplotpy
  No impacts to other repositories.

Enhancement Checklist

See the METplus Workflow for details.

• Complete the issue definition above.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update unit tests.
• Add/update documentation.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.