Implement aggregation of SEEPS data across multiple cases

[TatianaBurek]

Describe the Enhancement

MET development version 11.0.0-beta3 made several changes to the "stat" output including adding a new line types SEEPS and SEEPS_MPR

• Issue Enhance Point-Stat to compute SEEPS for point observations and write new SEEPS and SEEPS_MPR STAT line types. MET#1942 enhances Point-Stat to write new SEEPS and SEEPS_MPR line types. Both of these new line type should be added to the schema. Note that Enhance Point-Stat to compute SEEPS for point observations and write new SEEPS and SEEPS_MPR STAT line types. MET#1942 will enhance Grid-Stat to also compute the SEEPS line type, but should make no additional changes to the schema.

Need to include the implementation of these statistics to METcalcpy

Note that issue dtcenter/MET#2882 is making refinements and changes to the implementation of SEEPS in MET. Recommend holding off on this downstream work until work for that MET issue has been completed by @mpm-meto and/or @RachelNorth.

Corresponding issue dtcenter/METdataio/issues/119

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

Sub-Issues

Consider breaking the enhancement down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2799991

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)

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, METdataio, METviewer, METexpress, METcalcpy, METplotpy

Enhancement 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.
• 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 and merge your changes.
• Delete your fork or branch.
• Close this issue.