Describe the Enhancement

On 2/18/21, Eric Gilleland presented the G and G-Beta methods. Since they are derived from the Mean-Error-Distance, which is already included in the DMAP line type, they are easily added to that line type.

Here's a description of the methods provided in the SpatialVx package in R:
https://www.rdocumentation.org/packages/SpatialVx/versions/0.7-1/topics/Gbeta

Implementation considerations:

• Should beta be made configurable via the Grid-Stat config file?
• Work with Eric to confirm the proper way of aggregating scores from multiple runs together, and enhance the Stat-Analysis tool to do so.
• Add documentation and references about this method to the MET User's Guide. List equations in Appendix C.

Time Estimate

1 day.

Sub-Issues

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

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2702691

Define the Metadata

Assignee

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

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
• Define a METdatadb issue to handle the new DMAP columns.
  Load new DMAP columns for G and GBETA. METdataio#62
• Define a METviewer issue to plot the new DMAP columns:
  Add support for plotting new G and GBETA statistics. METviewer#324
• Define a METplus issue to make the setting of the beta_value option configurable:
  Add Grid-Stat configuration options for distance_map dictionary METplus#1089

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.