Enhance Point-Stat to compute SEEPS for point observations and write new SEEPS and SEEPS_MPR STAT line types.

[RachelNorth]

Describe the New Feature

The Stable Equitable Error in Probability Space (SEEPS) score is described in Rodwell et al. (2010) and was devised for evaluating quantitative precipitation forecasts against SYNOP gauge data at (but not limited to) station locations. It uses a climatology to account for local variations in rainfall which enables aggregation over otherwise heterogenous locations.

This issue will detail the work required to implement this capability within MET and to act as an umbrella issue to log progress as it is likely that implementing this will require division into further sub-issues.

Changes will be required to Point-Stat in order to compute the score.
Support for a point-based climatology will be required. MET #1941 has been opened for the work required for this capability.

This issue will supersede the SEEPS portion of MET #563.

This still needs more definition on how to implement.

The tasks for this work include:

• Enhance Point-Stat to compute SEEPS.
• Enhance Stat-Analysis to compute SEEPS from the matched pair (MPR) input lines.

There is no way to mathematically aggregate SEEPS over multiple runs. Instead we just compute the mean of the SEEPS over multiple runs.

We do still need to define the columns that should be included in a new SEEPS line type.

Acceptance Testing

List input data types and sources.
Input data expected to be either ASCII text or NetCDF files.
Original IDL code can be provided to compare scores. Example C code is provided in the google drive link at #563 (comment)

Time Estimate

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

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

2799991

Define the Metadata

Assignee

• Select engineer(s) or no engineer required @TaraJensen
• Select scientist(s) or no scientist required @RachelNorth, @mpm-meto

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

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.

[JohnHalleyGotway]

@hsoh-u, do the seeps point climo values in PPT24_seepsweights.nc ONLY apply to 24-hour accumulations of precip? I'm guessing that that's the case, but want to confirm.

If so we need to add that logic in Point-Stat. Right now, those climo values are being applied to 3-hourly accumulations in the Point-Stat unit tests. We'll need to update Point-Stat to only compute SEEPS for 24-hour accumulations of precip.

Of course, it'd make sense to handle climos for other accumulation intervals and/or other variable altogether. In the next round of development, we may want to rethink how we configure things. Perhaps we have the user specify the path to the point climo data file directly in the obs.field array entry (e.g. point_climo = "MET_BASE/climo/seeps/PPT24_seepsweights.nc";)? If its specified, we use that to compute seeps. If empty, we don't compute seeps. That'd make things more configurable for the user and also make the logic in the code much easier... just use whatever point climo data the user has provided.

[hsoh-u]

It's not checking if 24 hour precipitations. Rachel's recommendation was focusing 24 hours. SEEPS can be calculated for any accumulation length for which the user has an appropriate climatology.