Skip to content

Enhance Series-Analysis to compute statistics from the SEEPS STAT line type. #2269

@JohnHalleyGotway

Description

@JohnHalleyGotway

Describe the Enhancement

The SEEPS output from Point-Stat and Grid-Stat is configured by setting the corresponding output_flag.seeps and output_flag.seeps_mpr flags. In Series-Analysis, we'll need to add a setting for output_stats.seeps. This is an array of column names for the SEEPS statistics that should be written to the output.

Recommend supporting all SEEPS output columns:

output_flag = {
   seeps = ["TOTAL", "S12", "S13", "S21", "S23", "S31", "S32", "PF1", "PF2", "PF3", "PV1", "PV2", "PV3", "MEAN_FCST", "MEAN_OBS", "SEEPS" ];
}

But please confirm with @RachelNorth that this is correct.

Note that the column names mentioned above have been modified by #2882. Review those changes and update the description above prior to beginning this work.

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

Complete this work prior to the end of the Met Office contract at the end of March 2025.

Funding Source

Not specified.

Define the Metadata

Assignee

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.

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.

Metadata

Metadata

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions