Describe the New Feature

Wind direction verification is different from vector wind and wind speed verification. The specificity of wind direction verification is that wind direction and wind direction difference between forecast and observation need to be adjusted to (-180, +180] degree. The current VCNT and VL1L2 outputs don't support wind direction verifications of RMSE, Bias and MAE.

So here is the request list of new outputs:

1. N: the number of grid points

2. MSE (mean squared value of wind direction difference between the forecast and observed wind, this difference needs to be adjusted to (-180, +180] degree)
   DIR2_BAR=sum [(DIRf-DIRo)**2]/N, where DIRf-DIRo needs to be recalculated to (-180, +180], DIRf is forecast wind direction and DIRo is observation wind direction.

3. Mean Error (mean value of wind direction difference between the forecast and observed wind, this difference needs to be adjusted to (-180, +180] degree)
   DIR_BAR=sum(DIRf-DIRo)/N, where DIRf-DIRo needs to be recalculated to (-180, +180]

4. MAE (mean absolute value of wind direction difference between the forecast and observed wind, this difference needs to be adjusted to (-180, +180] degree)
   DIR_ABSBAR=sum[abs(DIRf-DIRo)]/N, where DIRf-DIRo needs to be recalculated to (-180, +180]

Meanwhile, the outputs will allow wind speed threshold settings.

Acceptance Testing

List input data types and sources.
Describe tests required for new functionality.

Time Estimate

2 days.

Sub-Issues

Consider breaking the new feature down into sub-issues.
None needed.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

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, METdataio, METviewer, METexpress, METcalcpy, METplotpy
• Add new wind direction verification statistics for RMSE, Bias, and MAE #2395
• Enhance METdataio schema to handle changes to the ECNT, VL1L2, VAL1L2, and VCNT line types during the MET 12.0.0 beta4 development cycle METdataio#282
• Enhance METcalcpy to aggregate statistics added to the ECNT, VL1L2, VAL1L2, and VCNT line types during the MET 12.0.0 beta4 development cycle METcalcpy#361
• Enhance METviewer to plot statistics added to the ECNT, VL1L2, VAL1L2, and VCNT line types introduced in the MET 12.0.0 beta4 development cycle METviewer#517

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