Describe the New Feature

In our discussions with CPC, we've been presented with NMME netCDF data files where all of the ensemble members are located in the same data structure in 1 file. CPC confirmed this is the normal structure for ensemble files, and has been encountered during work with other entities (e.g. NRL). While Python embedding is currently a viable solution to this file design type, there's a desire for MET's EnsembleStat tool to do this natively.

Acceptance Testing

Sample NMME file can be found on kiowa, under /d1/projects/MET/MET_test_data/CPC_NMME. Variables of interest are ensmem(ensmem) and fcst(ensmem,target,lat,lon)
Tests should successfully read in all ensemble members in datafile into EnsembleStat with available processing options mirroring what was available for individual member files.

Time Estimate

Estimate the amount of work required here.
Unknown until later date, input from Engineers

Sub-Issues

Consider breaking the new feature down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

None

Funding Source

TBD when on a beta schedule

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

• 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

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), Project(s), Milestone, and Linked issues
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.