Describe the Enhancement

When verifying ensembles the UK Met Office does not include the control member in the resulting ensemble statistics. This task is to coordinate with @mpm-meto and/or @robdarvell to determine how the Ensemble-Stat tool should handle a control member.

One big question is, if the control member is NOT included in the computation of statistics, who should it be used by Ensemble-Stat. Perhaps there is no need to pass it to Ensemble-Stat in the first place.

If we determine that a control member is needed and useful in Ensemble-Stat, enhance Ensemble-Stat to do so. Clearly, we need more discussion and definition here before this issue is actionable.

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

Can move to future development cycles and/or versions depending on when we get the task well-defined.

Funding Source

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, METdatadb, METviewer, METexpress, METcalcpy, METplotpy
• Add support for setting control members in EnsembleStat and GenEnsProd METplus#1236

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.