Describe the Enhancement

In the CNT line type, Anomaly Correlation Coefficient is part of the output from the line type. It would be good to add this to the VCNT line type, so that Anomaly Correlation Coefficient can be calculated for Vector Wind. See the bottom of slide 11 for the equation at https://www.emc.ncep.noaa.gov/users/verification/global/gfs/doc/RMSE_decomposition.pdf. Additionally, it can be computed from the VAL1L2 line type by the equation

A=sum[(uf-uc)(uo-uc)+(vf-vc)(vo-vc)]
B=sum[(uf-uc)**2+(vf-vc)**2]
C=sum[(uo-uc)**2+(vo-vc)**2]
ACC=A/sqrt(B*C)

uf = u wind forecast
uo = u wind observation
uc = u wind climatology
vf = v wind forecast
vo = v wind observation
vc = v wind climatology

or in terms from the VAL1L2 line type...

ACC = (UVFOABAR)/(sqrt(UVFFABAR*UVOOABAR)

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.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2793541, 2702691

Define the Metadata

Assignee

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

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.