New Use Case: Probability of Exceedence for 85th percentile temperatures

[j-opatz]

Describe the New Use Case

This is the result of a project with CPC to ingest Probability of Exceedence (POE) datasets and provide deterministic verification. After several iterations a comparison of 8 day lead to binary fields for the 85th percentile of temperature were settled on.

Use Case Name and Category

use case should follow GridStat_fcstGEFS_obsCADB_BinaryObsPOE for naming, and reside in the Medium Range category.

Input Data

Input sources are from GEFS (for both fields), and are in netCDF format. The fields are ingested via Python embedding.
Files are fairly small, with fcst -- 7.5 MB and obs -- 21KB.

Acceptance Testing

The use case should run successfully, with the requested output (CTC, CTS) being produced and filled with realistic values.
As use case develops, provide a run time here

Time Estimate

1-2 days

Sub-Issues

Consider breaking the new feature down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

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

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdatadb, METviewer, METexpress, METcalcpy, METplotpy

New Use Case Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding source.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Add any new Python packages to the METplus Components Python Requirements table.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Linked issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Iterate until the reviewer(s) accept your changes. Merge branch into develop.
• Create a second pull request to merge develop into develop-ref, following the same steps for the first pull request.
• Delete your fork or branch.
• Close this issue.