Describe the Enhancement

The issue dtcenter/MET#1673 and corresponding pull request dtcenter/MET#1857 add new columns to the distance map (DMAP) line type created by the Grid-Stat tool.

This adds 3 new columns to the end of the existing DMAP line type: G, GBETA, and BETA_VALUE. All 3 columns are floating point numbers. METviewer should be enhanced to plot the G and GBETA statistics. The BETA_VALUE is informational and likely does not need to be plotted. G and GBETA do not need to be aggregated across multiple cases. Instead, just plot them using summary options, like mean and median.

Note that G will always have a value in the output, but GBETA and BETA_VALUE will only have a value when VX_MASK = FULL. When VX_MASK != FULL, GBETA = BETA_VALUE = NA.

Check with @ericgilleland (also assigned to this issue) to see if METviewer should be enhanced to error out or print a warning message when plotting GBETA while the corresponding BETA_VALUE changes. Also, @ericgilleland should confirm that G and GBETA should not be aggregated over multiple cases in some way... and that computing summary statistics is appropriate.

Please see METdatadb issue for loading this new output into the statistics database:
dtcenter/METdataio#62

Corresponding issue in METplotpy:
dtcenter/METplotpy#142

Please see existing documentation for more details about the configuration options, science, and equations.

Sample data can be found in kiowa:/d1/projects/MET/MET_regression/develop/NB20210818/MET-develop/test_output/met_test_scripts/grid_stat/grid_stat_120000L_20050807_120000V_dmap.txt.

Time Estimate

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

Sub-Issues

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

Relevant Deadlines

Prior to the coordinated METplus 4.1.0 release.

Funding Source

2702691

Define the Metadata

Assignee

• Select engineer(s) or no engineer required: Tatiana
• Select scientist(s) or no scientist required: Eric

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

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 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.