New Use Case: Demonstrate new forecast climatology feature

[j-opatz]

Describe the New Use Case

With the newest feature of MET offering users the opportunity to utilize separate climatologies for forecast and observational datasets, a new use case is being created to demonstrate this capability. Data is provided from EMC and coordinated through Gwen and Amandeep.

Use Case Name and Category

As this is verifying forecasts with multiple climatologies and applies to the CFSv2 datasets, the use case will reside in the S2S category.
Naming of the use case will follow:
GridStat_fcstCFSv2_obsERA5_climoCFSv2andERA5_separateClimo

Input Data

Fcst: CFSv2 data (2m temp fields)
Obs: ERA5
Fcst climo: CFSv2 monthly files
Obs climo: ERA5 monthly files

Acceptance Testing

Describe tests required for new functionality.
As use case develops, provide a run time here

Time Estimate

7-10 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

• Review default alert labels
• Select component(s)
• Select priority
• Select requestor(s)
• Select privacy

Milestone and Projects

• Select Milestone as a METplus-Wrappers-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
• For a METplus-Wrappers-X.Y.Z version, select the METplus-Wrappers-X.Y.Z Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, 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.
• For any new datasets, an entry to the METplus Verification Datasets Guide.
• 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 Development issue
  Select: Milestone as the next official version
  Select: METplus-Wrappers-X.Y.Z Development project for development toward the next official release
• 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.