New Use Case: Hurricane Matthew using native WRF

[georgemccabe]

In the METplus Engineering meeting on May 7, 2024, we discussed adding a new use case to demonstrate reading native WRF data into MET.

Describe the New Use Case

The use case that is being developed for I-WRF (https://github.com/NCAR/i-wrf/issues/48) would make a good example.

Use Case Name and Category

Provide use case name, following Contributor's Guide naming template, and list which category the use case will reside in. If a new category is needed for this use case, provide its name and brief justification

Input Data

List input data types and sources. Provide a total input file size, keeping necessary data to a minimum.

Acceptance Testing

Describe tests required for new functionality. As use case develops, provide a run time here

Time Estimate

Estimate the amount of work required here. Issues should represent approximately 1 to 3 days of work.

Sub-Issues

Consider breaking the new feature down into sub-issues.

• [ ] Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

I-WRF

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)
• [ ] Select privacy

Projects and Milestone

• [ ] Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE 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

New Use Case 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.
• [ ] Add any new Python packages to the METplus Components Python Requirements table.
• [ ] 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 your changes. Merge branch into develop.
• [ ] Create a second pull request to merge develop into develop-ref, following the same steps for the first pull request.
• [ ] Delete your fork or branch.
• [ ] Close this issue.