Describe the Enhancement

This is a request from NRL submitted via met-help:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97623

At Debug(3), Point-Stat prints out counts of reason codes listing why observations were excluded from each verification task, as shown below.

When discarding observations based on topography differences, a detailed Debug(4) level message is logged explaining why. This task is to enhance vx_statistics/pair_data_point.cc with additional Debug(4) detailed log messages for other types of observation exclusions.

718 DEBUG 3: Number of matched pairs = 1292
719 DEBUG 3: Observations processed = 19696
720 DEBUG 3: Rejected: SID exclusion = 0
721 DEBUG 3: Rejected: obs type = 16198
722 DEBUG 3: Rejected: valid time = 0
723 DEBUG 3: Rejected: bad obs value = 0
724 DEBUG 3: Rejected: off the grid = 355
725 DEBUG 3: Rejected: topography = 665
726 DEBUG 3: Rejected: level mismatch = 0
727 DEBUG 3: Rejected: quality marker = 0
728 DEBUG 3: Rejected: message type = 0
729 DEBUG 3: Rejected: masking region = 0
730 DEBUG 3: Rejected: bad fcst value = 1186
731 DEBUG 3: Rejected: duplicates = 0
732 DEBUG 2: Computing Continuous Statistics.

Add detailed log messages for:
bad obs value, off the grid, topography (already present), bad fcst value, duplicates

Do not add detailed log message for:
SID exclusion, obs type, valid time, level mismatch, quality marker, message type, masking region

We are weighing useful log messages vs swamping the user with too many messages. The latter reasons are easily investigated by re-configuring/re-running Point-Stat. The former set cannot be easily investigated in this way.

Time Estimate

4 hours.

Sub-Issues

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

Relevant Deadlines

None

Funding Source

NRL

Define the Metadata

Assignee

• Select engineer(s) or no engineer required: John HG
• Select scientist(s) or no scientist required: no scientist required

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Review projects and select relevant Repository and Organization ones or add "alert:NEED PROJECT ASSIGNMENT" label
• Select milestone to next major version milestone or "Future Versions"

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdatadb, METviewer, METexpress, METcalcpy, METplotpy
  No impacts.

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), Project(s), Milestone, and Linked issues
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.