Describe the Enhancement

#2206 added the CRPS_EMP_FAIR statistic to the ECNT line type in MET-11.0.0-beta3. While doing that development, we overlooked this comment from @RogerHar.

This issue is to remedy that by adding the mean absolute difference statistic to the ECNT line type as an alternative measure of ensemble spread.

The development for #2206 already added the computation of the ensemble mean absolute difference. So this task is largely administrative, adding this statistics to the ECNT output line type and ensuring that Stat-Analysis can read/aggregate it over multiple cases.

Please see this reference:
Hopson, T. M. (2014). Assessing the Ensemble Spread–Error Relationship, Monthly Weather Review, 142(3), 1125-1142. DOI: 10.1175/MWR-D-12-00111.1

Time Estimate

4 hours.

Sub-Issues

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

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

UK MetOffice 2799991

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
  Will update existing issues with this information:
  • Update the database schema to handle new columns and line types added to the MET-11.0.0-beta4 output. METdataio#131
  • Plot the new ECNT statistics: SPREAD_MD, MAE, MAE_OERR, BIAS_RATIO, ME_GE_OBS, and ME_LT_OBS METviewer#434
  • Implement aggregation of the new ECNT statistics: SPREAD_MD, MAE, MAE_OERR, BIAS_RATIO, N_GE_OBS, ME_GE_OBS, N_LT_OBS, and ME_LT_OBS METcalcpy#229

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.