Describe the Enhancement

#3006 added the initial version of the Pair-Stat tool for the MET-12.1.0-beta1 release. This issue is to extend the functionality of Pair-Stat as described below:

• Add support for the -format ioda command line option along with a unit test to demonstrate.
• Track metadata from IODA inputs to populate the output STAT header columns well.
• Add configuration option(s) to filter input pair data by time.
• Add support for attaching climo_mean/climo_stdev to the pairs.
• Add support for the -format python command line option along with a unit test to demonstrate.
• Complete the documentation for this new tool.
• Refine the way spatial masking is handled.
  • Currently, all grid and poly masks are mapped to a global 1/10 degree grid, but leads to inconsistent application of masking regions at the edges. Instead, let the grid vary for each masking region.
  • NOTE: This item was not completed for this issue but could be done as future work.

Time Estimate

~ 1 week?

Sub-Issues

Consider breaking the enhancement down into sub-issues.
None needed.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Per @DanielAdriaansen, charge up to 20 hours to NRL METPLUS 7730022 by Friday, 28 March 2025.

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Review default alert labels
• Select component(s)
• Select priority
• Select requestor(s)

Milestone and Projects

• Select Milestone as a MET-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
• For a MET-X.Y.Z version, select the MET-X.Y.Z Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy
  No impacts expected.

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 Development issue
  Select: Milestone as the next official version
  Select: MET-X.Y.Z Development project for development toward the next official release
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.