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: Stratosphere QBO #2557

Closed
24 tasks
CPKalb opened this issue Apr 18, 2024 · 0 comments · Fixed by #2621
Closed
24 tasks

New Use Case: Stratosphere QBO #2557

CPKalb opened this issue Apr 18, 2024 · 0 comments · Fixed by #2621
Assignees
Labels
priority: high High Priority type: new use case Add a new use case
Milestone

Comments

@CPKalb
Copy link
Contributor

CPKalb commented Apr 18, 2024

Describe the New Use Case

The new use case will calculate QBO and create plots

Use Case Name and Category

s2s_stratosphere/UserScript_fcst_obsERA_StratosphereQBO

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.
Longer than 3 days

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

Contact Tara for key each timecard

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.
@CPKalb CPKalb 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 Apr 18, 2024
@CPKalb CPKalb self-assigned this Apr 18, 2024
@CPKalb CPKalb moved this from 🔖 Ready to 🏗 In progress in METplus-Wrappers-6.0.0 Development May 22, 2024
@CPKalb CPKalb added this to the METplus-6.0.0 milestone May 22, 2024
@CPKalb CPKalb added priority: high High Priority and removed alert: NEED CYCLE ASSIGNMENT Need to assign to a release development cycle labels May 22, 2024
@CPKalb CPKalb linked a pull request Jun 25, 2024 that will close this issue
16 tasks
@CPKalb CPKalb moved this from 🏗 In progress to ✅ Done in METplus-Wrappers-6.0.0 Development Jun 28, 2024
@CPKalb CPKalb removed alert: NEED MORE DEFINITION Not yet actionable, additional definition required alert: NEED ACCOUNT KEY Need to assign an account key to this issue labels Jun 28, 2024
@CPKalb CPKalb closed this as completed Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high High Priority type: new use case Add a new use case
Projects
No open projects
Status: 🏁 Done
Development

Successfully merging a pull request may close this issue.

1 participant