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

Import additional Zonal and Meridional Means into METplus #1342

Open
21 tasks
CPKalb opened this issue Jan 7, 2022 · 1 comment
Open
21 tasks

Import additional Zonal and Meridional Means into METplus #1342

CPKalb opened this issue Jan 7, 2022 · 1 comment
Assignees
Labels
alert: NEED MORE DEFINITION Not yet actionable, additional definition required type: new feature Make it do something new

Comments

@CPKalb
Copy link
Contributor

CPKalb commented Jan 7, 2022

Describe the New Feature

Incorporate the the more complex zonal and meridional means (fromhttps://github.com/zdlawrence/pyzome/blob/master/pyzome/recipes.py ) needed to compute stratospheric metrics into METplus.

Acceptance Testing

I've been testing with the ERA on glade, but this was also suggested: https://www.ncei.noaa.gov/data/sudden-stratospheric-warming-compendium/access/

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.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2793541

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.

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) 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.
@CPKalb CPKalb added type: new feature Make it do something new 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 labels Jan 7, 2022
@CPKalb CPKalb 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 Jan 7, 2022
@CPKalb CPKalb closed this as completed Aug 17, 2022
@CPKalb
Copy link
Contributor Author

CPKalb commented Aug 17, 2022

This the the METplus issue to go along with METcalcpy issue 133

@CPKalb CPKalb reopened this Aug 17, 2022
@hankenstein2 hankenstein2 removed their assignment May 15, 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 type: new feature Make it do something new
Projects
None yet
Development

No branches or pull requests

2 participants