Feature #2339 stat_analysis_seeps

[JohnHalleyGotway]

@hsoh-u I'd like to merge my Stat-Analysis changes for SEEPS back into your feature branch.
** IMPORTANT ** there's memory management problems in computing the seeps density that are fixed here using STL vectors.

These Stat-Analysis change include...

• Supporting -job filter for -line_type SEEPS and -line_type SEEPS_MPR.
• Supporting -job summary for columns in SEEPS and/or SEEPS_MPR.
• Supporting -job aggregate for -line_type SEEPS.
• Supporting -job aggregate_stat for -line_type SEEPS_MPR -out_line_type SEEPS.
• Add tests to test_unit/xml/unit_stat_analysis_ps.xml to demonstrate.
• Update User's Guide Stat-Analysis chapter to list the supported SEEPS functions.

Expected Differences

• Do these changes introduce new tools, command line arguments, or configuration file options? [No]
  
  If yes, please describe:
  

• Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [No]
  
  If yes, please describe:
  

Pull Request Testing

• Describe testing already performed for these changes:
  
  The Stat-Analysis jobs that I added demonstrate that the filtering, summary, and aggregation logic.
  But that logic is VERY simplistic.

  • Aggregates all SEEPS columns (S12 S13 S21 S23 S31 S32 PF1 PF2 PF3 PV1 PV2 PV3 MEAN_FCST MEAN_OBS SEEPS) as weighted averages where the weight is defined by the TOTAL column.
  • To aggregate SEEPS_MPR to SEEPS, it loads the SEEPS_MPR data into a PairDataPoint object and calls the library code toe compute SEEPS.

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  

  • Biggest question is the aggregation logic. I think this simple approach is fine for most columns. But I have NO IDEA about the S, PF, and PV columns. Those are written as 0 in the output of Stat-Analysis. Once you have their contents figured out, we should review/revise the aggregation logic as needed.

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes]

• Do these changes include sufficient testing updates? [Yes]

• Will this PR result in changes to the test suite? [Yes]
  
  If yes, describe the new output and/or changes to the existing output:
  
  Adds new Stat-Analysis output.

• Please complete this pull request review by [Mon 11/14/22].
  

Pull Request Checklist

See the METplus Workflow for details.

• Review the source issue metadata (required labels, projects, and milestone).
• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Define the PR metadata, as permissions allow.
  Select: Reviewer(s)
  Select: Organization level software support Project or Repository level development cycle Project
  Select: Milestone as the version that will include these changes
• After submitting the PR, select Development with the original issue number.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.

[JohnHalleyGotway]

@hsoh-u, FYI, I saw an error in the docker build step as well as a documentation warning message. I've fixed both in my feature branch and will let GHA finish running to confirm that the fixes work as expected.