Enhance Stat-Analysis to aggregate SEEPS_MPR and SEEPS line types.

[JohnHalleyGotway]

Describe the Enhancement

• MET Enhance Point-Stat to compute SEEPS for point observations and write new SEEPS and SEEPS_MPR STAT line types. #1942 enhances Point-Stat to write the SEEPS and SEEPS_MPR line types when verifying against point observations.
• MET Enhance Grid-Stat to compute SEEPS for gridded observations and write the SEEPS STAT line type. #1943 enhances Grid-Stat to write the SEEPS line types when doing grid-to-grid comparisons. Also consider writing SEEPS_MPR information to the "_ncpairs.nc" output file.
• This issue is to enhance Stat-Analysis to aggregate these new line types as described below:

1. -job aggregate -line_type SEEPS
2. -job aggregate_stat -line_type SEEPS_MPR -out_line_type SEEPS

Acceptance Testing

List input data types and sources.
Describe tests required for new functionality.

Time Estimate

Estimate the amount of work required here.
Unknown

Sub-Issues

Consider breaking the new feature down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

Funding Source

2799991

Define the Metadata

Assignee

• Select engineer(s) or no engineer required: @JohnHalleyGotway
• Select scientist(s) or no scientist required: @RachelNorth

Labels

• Select component(s)
• Select priority medium-to-high
• Select requestor(s) UK Met Office

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
  No specific METplus changes needed.
• Write METcalcpy issue to add support for aggregating SEEPS to a future release.

New Feature 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.