Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Use Case: Hurricane Matthew using native WRF #2577

Open
24 tasks
georgemccabe opened this issue May 7, 2024 · 0 comments
Open
24 tasks

New Use Case: Hurricane Matthew using native WRF #2577

georgemccabe opened this issue May 7, 2024 · 0 comments
Assignees
Labels
alert: NEED MORE DEFINITION Not yet actionable, additional definition required component: python wrapper priority: high High Priority type: new use case Add a new use case
Milestone

Comments

@georgemccabe
Copy link
Collaborator

georgemccabe commented May 7, 2024

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 (NCAR/i-wrf#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.

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.
@georgemccabe georgemccabe added alert: NEED MORE DEFINITION Not yet actionable, additional definition required alert: NEED ACCOUNT KEY Need to assign an account key to this issue alert: NEED CYCLE ASSIGNMENT Need to assign to a release development cycle type: new use case Add a new use case labels May 7, 2024
@georgemccabe georgemccabe added this to the METplus-6.0.0 milestone May 7, 2024
@georgemccabe georgemccabe self-assigned this May 7, 2024
@georgemccabe georgemccabe added component: python wrapper and removed alert: NEED ACCOUNT KEY Need to assign an account key to this issue alert: NEED CYCLE ASSIGNMENT Need to assign to a release development cycle labels May 7, 2024
@JohnHalleyGotway JohnHalleyGotway added the priority: high High Priority label May 15, 2024
@georgemccabe georgemccabe moved this from 🩺 Needs Triage to 🟢 Ready in METplus-Analysis-6.1.0 Development Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alert: NEED MORE DEFINITION Not yet actionable, additional definition required component: python wrapper priority: high High Priority type: new use case Add a new use case
Projects
Status: 🟢 Ready
Development

No branches or pull requests

2 participants